From 3fd66d341b9de0e17f1f87e969ca11a780b137f6 Mon Sep 17 00:00:00 2001 From: Kalaiselvi Murugesan Date: Fri, 8 Sep 2023 20:49:39 +0000 Subject: [PATCH 1/4] Update: Allocation Overflow Documentation --- examples/fleet.yaml | 4 ++-- site/content/en/docs/Reference/fleet.md | 5 ++++- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/examples/fleet.yaml b/examples/fleet.yaml index 8c313146a2..66f1622d05 100644 --- a/examples/fleet.yaml +++ b/examples/fleet.yaml @@ -52,8 +52,8 @@ spec: maxUnavailable: 25% # [Stage:Alpha] # [FeatureFlag:FleetAllocationOverflow] - # Labels and/or Annotations to apply to overflowing GameServers when the number of Allocated GameServers is more - # than the desired replicas on the underlying `GameServerSet` + # Labels and/or Annotations to apply to overflowing GameServers when the number of Allocated GameServers exceeds + # the desired replicas in the underlying `GameServerSet` # Commented out since Alpha, and disabled by default # allocationOverflow: # labels: diff --git a/site/content/en/docs/Reference/fleet.md b/site/content/en/docs/Reference/fleet.md index 852b773cb6..1b7604e655 100644 --- a/site/content/en/docs/Reference/fleet.md +++ b/site/content/en/docs/Reference/fleet.md @@ -109,10 +109,13 @@ The `spec` field is the actual `Fleet` specification and it is composed as follo - `maxSurge` is the amount to increment the new GameServers by. Defaults to 25% - `maxUnavailable` is the amount to decrements GameServers by. Defaults to 25% - `allocationOverflow` (Alpha, requires `FleetAllocationOverflow` flag) The labels and/or Annotations to apply to - GameServers when the number of Allocated GameServers drops below the desired replicas on the underlying + GameServers when the number of Allocated GameServers exceeds the desired replicas in the underlying `GameServerSet`. - `labels` the map of labels to be applied - `annotations` the map of annotations to be applied + - `Fleet's Scheduling Strategy`: The GameServers associated with the GameServerSet are sorted based on either `Packed` or `Distributed` strategy. + - `Packed`: Agones maximizes resource utilization by trying to populate nodes that are already in use before allocating GameServers to other nodes. + - `Distributed`: Agones employs this strategy to spread out GameServer allocations, ensuring an even distribution of GameServers across the available nodes. - `template` a full `GameServer` configuration template. See the [GameServer]({{< relref "gameserver.md" >}}) reference for all available fields. From c7c483b658c00a608bf4f28372d9ca56fcb32ea3 Mon Sep 17 00:00:00 2001 From: Kalaiselvi Murugesan Date: Tue, 12 Sep 2023 04:32:43 +0000 Subject: [PATCH 2/4] updated fleet document --- site/content/en/docs/Guides/fleet-updates.md | 1 + 1 file changed, 1 insertion(+) diff --git a/site/content/en/docs/Guides/fleet-updates.md b/site/content/en/docs/Guides/fleet-updates.md index f195eb52ae..0f8087dc32 100644 --- a/site/content/en/docs/Guides/fleet-updates.md +++ b/site/content/en/docs/Guides/fleet-updates.md @@ -147,6 +147,7 @@ This provides two useful capabilities: 2. This can also be used to proactively update `GameServer` labels, to effect change in allocation strategy - such as preferring the newer `GameServers` when allocating, but falling back to the older version if there aren't enough of the new ones yet spun up. +The labels and/or annotations are applied to `GameServers` in a `Fleet` in the order designated by their configured [Fleet scheduling]({{< ref "/docs/Advanced/scheduling-and-autoscaling#fleet-scheduling">}}) Example yaml configuration: From ad825f15b1d9ec272291d95fad1e0d14d53d5950 Mon Sep 17 00:00:00 2001 From: Kalaiselvi Murugesan Date: Tue, 12 Sep 2023 19:24:08 +0000 Subject: [PATCH 3/4] \n added --- site/content/en/docs/Guides/fleet-updates.md | 1 + 1 file changed, 1 insertion(+) diff --git a/site/content/en/docs/Guides/fleet-updates.md b/site/content/en/docs/Guides/fleet-updates.md index 0f8087dc32..1ae22c9d2a 100644 --- a/site/content/en/docs/Guides/fleet-updates.md +++ b/site/content/en/docs/Guides/fleet-updates.md @@ -147,6 +147,7 @@ This provides two useful capabilities: 2. This can also be used to proactively update `GameServer` labels, to effect change in allocation strategy - such as preferring the newer `GameServers` when allocating, but falling back to the older version if there aren't enough of the new ones yet spun up. + The labels and/or annotations are applied to `GameServers` in a `Fleet` in the order designated by their configured [Fleet scheduling]({{< ref "/docs/Advanced/scheduling-and-autoscaling#fleet-scheduling">}}) Example yaml configuration: From 927fa6c751c74949fcea5cb836a5b0c1051d7ddf Mon Sep 17 00:00:00 2001 From: Kalaiselvi Murugesan Date: Tue, 12 Sep 2023 21:21:58 +0000 Subject: [PATCH 4/4] small nit --- site/content/en/docs/Guides/fleet-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/en/docs/Guides/fleet-updates.md b/site/content/en/docs/Guides/fleet-updates.md index 1ae22c9d2a..e94fdae742 100644 --- a/site/content/en/docs/Guides/fleet-updates.md +++ b/site/content/en/docs/Guides/fleet-updates.md @@ -148,7 +148,7 @@ This provides two useful capabilities: preferring the newer `GameServers` when allocating, but falling back to the older version if there aren't enough of the new ones yet spun up. -The labels and/or annotations are applied to `GameServers` in a `Fleet` in the order designated by their configured [Fleet scheduling]({{< ref "/docs/Advanced/scheduling-and-autoscaling#fleet-scheduling">}}) +The labels and/or annotations are applied to `GameServers` in a `Fleet` in the order designated by their configured [Fleet scheduling]({{< ref "/docs/Advanced/scheduling-and-autoscaling#fleet-scheduling">}}). Example yaml configuration: