Create Kubernetes Cluster
Instructions for creating a Kubernetes cluster to install Agones on.
Install and configure Agones on Kubernetes
Instructions for creating a Kubernetes cluster and installing Agones.
Usage Requirements
- Kubernetes cluster version 1.23, 1.24, 1.25
- Google Kubernetes Engine, Azure Kubernetes Service, Amazon EKS and Minikube are supported.
- If you are creating and managing your own Kubernetes cluster, the
MutatingAdmissionWebhook, and
ValidatingAdmissionWebhook
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.
Warning
This release has been tested against Kubernetes versions 1.23, 1.24, 1.25 on GKE. Other versions may work, but are unsupported. It is also likely that not all of these versions are supported by other cloud providers.Supported Container Architectures
The following container operating systems and architectures can be utilised with Agones:
| OS | Architecture | Support |
|---|---|---|
| linux | amd64 |
Stable |
| linux | arm64 |
Alpha |
| windows | amd64 |
Alpha |
For all the platforms in Alpha, we would appreciate testing and bug reports on any issue found.
Agones and Kubernetes Supported Versions
Agones will support 3 releases of Kubernetes, targeting the newest version as being the default version in the GKE Rapid channel. However, we will ensure that at least one of the 3 versions chosen for each Agones release is supported by each of the major cloud providers (EKS and AKS). The vendored version of client-go will be aligned with the middle of the three supported Kubernetes versions. When a new version of Agones supports new versions of Kubernetes, it is explicitly called out in the release notes.
The following table lists recent Agones versions and their corresponding required Kubernetes versions:
| Agones version | Kubernetes version(s) |
|---|---|
| 1.30 | 1.23, 1.24, 1.25 |
| 1.29 | 1.24 |
| 1.28 | 1.23 |
| 1.27 | 1.23 |
| 1.26 | 1.23 |
| 1.25 | 1.22 |
| 1.24 | 1.22 |
| 1.23 | 1.22 |
| 1.22 | 1.21 |
| 1.21 | 1.21 |
Best Practices
Separation of Agones from GameServer nodes
When 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=true and tolerates the node taint agones.dev/agones-system=true:NoExecute.
If no dedicated nodes are available, Agones will run on regular nodes.
Install Agones
Install Agones in your existing Kubernetes cluster.
Deploy Kubernetes cluster and install Agones using Terraform
Install a Kubernetes cluster and Agones declaratively using Terraform.
Confirming Agones Installation
Verify Agones is installed and has started successfully.
Upgrading Agones and Kubernetes
Strategies and techniques for managing Agones and Kubernetes upgrades in a safe manner.
Feedback
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 March 29, 2023: Helm test content update in Agones doc (#3052) (60f72f0)