This page provides a description of the various stages that Agones features can be in, and the relative maturity and support level expected for each level.
Best practices for running Agones in production.
The SDKs are integration points for game servers with Agones itself.
GameServers on Kubernetes nodes with the Windows operating system.
Common patterns and approaches for updating Fleets with newer and/or different versions of your
Health checking exists to track the overall healthy state of the GameServer, such that action can be taken when a something goes wrong or a GameServer drops into an Unhealthy state
Track player connections, disconnections, counts and capacities through the Agones SDK
Register your local game server with Agones.
When running multiple Agones clusters around the world, you may need to have clients determine which cluster to connect to based on latency.
It’s likely that we will want to programmatically interact with Agones. Everything that can be done via the
kubectl and yaml configurations can also be done via the Kubernetes API.
Troubleshooting guides and steps.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.
Last modified February 20, 2024: Document `Distributed` pod scheduling. (#3662) (24e7f83)