-
Notifications
You must be signed in to change notification settings - Fork 813
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: Game Server Allocation Details #3583
Conversation
Build Succeeded 👏 Build Id: ab6a5350-7dce-42d8-9675-5878b34bb8a8 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
@markmandel, I have updated the |
Build Failed 😱 Build Id: a1a7be14-68f1-4bc1-88c5-01ca0c2bdf48 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Succeeded 👏 Build Id: c6914b7e-ff7e-4c8d-884b-859a3b6ff629 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
@@ -7,6 +7,10 @@ description: "A `GameServerAllocation` is used to atomically allocate a GameServ | |||
weight: 30 | |||
--- | |||
|
|||
{{% feature publishVersion="1.38.0" %}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need for a feature flag - feature flags are only for when we talk about a feature that hasn't been released yet. Updated/improvements to existing docs for existing features don't need it.
@@ -7,6 +7,10 @@ description: "A `GameServerAllocation` is used to atomically allocate a GameServ | |||
weight: 30 | |||
--- | |||
|
|||
{{% feature publishVersion="1.38.0" %}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this place better for this documentation improvement! 👍🏻
@@ -7,6 +7,10 @@ description: "A `GameServerAllocation` is used to atomically allocate a GameServ | |||
weight: 30 | |||
--- | |||
|
|||
{{% feature publishVersion="1.38.0" %}} | |||
When we have a fleet of game servers ready, allocation is the process of selecting a one of these servers for use. This is achieved using a `GameServerAllocation`. The allocation process marks the chosen game server for gameplay and marks it as `Allocated`. This ensures that the server is reserved for active players and not considered `ready` for other allocations until `SDK.Shutdown()` is called, or it is manually deleted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When we have a fleet of game servers ready, allocation is the process of selecting a one of these servers for use. This is achieved using a `GameServerAllocation`. The allocation process marks the chosen game server for gameplay and marks it as `Allocated`. This ensures that the server is reserved for active players and not considered `ready` for other allocations until `SDK.Shutdown()` is called, or it is manually deleted. | |
Allocation is the process of selecting the optimal `GameServer` that matches the filters defined in the `GameServerAllocation` specification below, and returning its details. | |
A successful Alloction moves the `GameServer` to the `Allocated` state, which demarcates that it is currently active, likely with players on it, and should not be removed until SDK.Shutdown() is called, or it is explicitly manually deleted. |
Some tweaks to the language.
@roberthbailey, @Kalaiselvi84 WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated this change. Shall we include this info in FAQ page?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the answer is no
. Shall we merge this PR?
Build Succeeded 👏 Build Id: f1ab4dab-d657-42e7-892e-3f3fa0d5c4b9 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Build Succeeded 👏 Build Id: 03692ca0-fbfe-4e6c-88d4-6dc2539c5cd6 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Build Succeeded 👏 Build Id: 679494a5-83e4-411d-b41e-ec86b0a2aaa4 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Build Succeeded 👏 Build Id: ba1d9d53-3f2c-4bf9-8789-d865d6d976c5 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
What type of PR is this?
/kind documentation
What this PR does / Why we need it:
Which issue(s) this PR fixes:
Closes #
Special notes for your reviewer: