Instructions for creating a Kubernetes cluster to install Agones on.
Install and configure Agones on Kubernetes
- Kubernetes cluster version 1.13
- Google Kubernetes Engine, Azure Kubernetes Service, Amazon EKS and Minikube have been tested
- If you are creating and managing your own Kubernetes cluster, the
admission controllers are required.
- We also recommend following the recommended set of admission controllers.
- Firewall access for the range of ports that Game Servers can be connected to in the cluster.
- Game Servers must have the game server SDK integrated, to manage Game Server state, health checking, etc.
WarningLater versions of Kubernetes may work, but this project is tested against 1.13, and is therefore the supported version. Agones will update its support to n-1 version of what is available across all major cloud providers - GKE, EKS and AKS
NoteWhen running in production, Agones should be scheduled on a dedicated pool of nodes, distinct from where Game Servers are scheduled for better isolation and resiliency. By default Agones prefers to be scheduled on nodes labeled with
agones.dev/agones-system=trueand tolerates the node taint
agones.dev/agones-system=true:NoExecute. If no dedicated nodes are available, Agones will run on regular nodes.
Install Agones in your existing Kubernetes cluster.
Install a Kubernetes cluster and Agones declaratively using Terraform.
Verify Agones is installed and has started successfully.
Strategies and techniques for managing Agones and Kubernetes upgrades in a safe manner.
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.