You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allocation policy CRD is currently only exposing the LoadBalancer service endpoint for allocator service and not the namespace. This works fine if there is an allocator service for each namespace that game servers are deployed to #854.
However, currently, there is only one allocator service deployed to agones-system namespace and it is assumed that all clusters in multi-cluster scenario are using the same namespace name for deploying game servers.
The solution is to expose namespace in allocation policy.
[Bonus: This also enables A/B testing on the same cluster by deploying two version of game servers and setting weight on allocation policy to redirect a percentage of traffic to a namespace in the cluster.]
The text was updated successfully, but these errors were encountered:
Allocation policy CRD is currently only exposing the LoadBalancer service endpoint for allocator service and not the namespace. This works fine if there is an allocator service for each namespace that game servers are deployed to #854.
However, currently, there is only one allocator service deployed to agones-system namespace and it is assumed that all clusters in multi-cluster scenario are using the same namespace name for deploying game servers.
The solution is to expose namespace in allocation policy.
[Bonus: This also enables A/B testing on the same cluster by deploying two version of game servers and setting weight on allocation policy to redirect a percentage of traffic to a namespace in the cluster.]
The text was updated successfully, but these errors were encountered: