Skip to content

Commit

Permalink
Revert "[Doc] Mark multicluster allocation feature as stable" (google…
Browse files Browse the repository at this point in the history
…forgames#1842)

* Revert "[Doc] Mark multicluster allocation feature as stable (googleforgames#1831)"

This reverts commit c575f40.

* Update multi-cluster-allocation.md

* Update multi-cluster-allocation.md

* Update feature-stages.md

* Update multi-cluster-allocation.md

* Update feature-stages.md
  • Loading branch information
pooneh-m authored and ilkercelikyilmaz committed Oct 23, 2020
1 parent a99ccf5 commit d69a5d5
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 0 deletions.
4 changes: 4 additions & 0 deletions site/content/en/docs/Advanced/multi-cluster-allocation.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,10 @@ description: >
In order to allow allocation from multiple clusters, Agones provides a mechanism to set redirect rules for allocation requests to the right cluster.
---

{{< alert title="Beta" color="warning">}}
This feature is in a pre-release state and might change.
{{< /alert >}}

There may be different types of clusters, such as on-premise, and Google Kubernetes Engine (GKE), used by a game to help with the cost-saving and availability.
For this purpose, Agones provides a mechanism to define priorities on the clusters. Priorities are defined on {{< ghlink href="pkg/apis/multicluster/v1/gameserverallocationpolicy.go" >}}GameServerAllocationPolicy{{< /ghlink >}} agones CRD. A matchmaker can enable the multi-cluster rules on a request and target [agones-allocator]({{< relref "allocator-service.md">}}) endpoint in any of the clusters and get resources allocated on the cluster with the highest priority. If the cluster with the highest priority is overloaded, the allocation request is redirected to the cluster with the next highest priority.

Expand Down
4 changes: 4 additions & 0 deletions site/content/en/docs/Guides/feature-stages.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,12 +26,16 @@ The current set of `alpha` and `beta` feature gates are:

| Feature Name | Gate | Default | Stage | Since |
|--------------|---------|---------|-------|-------|
| Multicluster Allocation<sup>*</sup> | N/A | Enabled | `Beta` | 1.6.0 |
| Example Gate (not in use) | `Example` | Disabled | None | 0.13.0 |
| [Port Allocations to Multiple Containers]({{< ref "/docs/Reference/gameserver.md" >}}) | `ContainerPortAllocation` | Enabled | `Beta` | 1.7.0 |
| [Player Tracking]({{< ref "/docs/Guides/player-tracking.md" >}}) | `PlayerTracking` | Disabled | `Alpha` | 1.6.0 |
| [SDK Send GameServer on Watch execution]({{< ref "/docs/Guides/Client SDKs/_index.md#watchgameserverfunctiongameserver" >}}) | `SDKWatchSendOnExecute` | Disabled | `Alpha` | 1.7.0 |
| Fix for RollingUpdate [Scale down](https://github.com/googleforgames/agones/issues/1625) and additional [details]({{< ref "/docs/Guides/fleet-updates.md#alpha-feature-rollingupdateonready" >}}) | `RollingUpdateOnReady` | Disabled | `Alpha` | 1.9.0 |

<sup>*</sup>Multicluster Allocation was started before this process was in place, and therefore does not have a
feature gate and cannot be disabled.

## Description of Stages

### Alpha
Expand Down

0 comments on commit d69a5d5

Please sign in to comment.