Create Kubernetes Cluster on Agones

Google Kubernetes Engine

Mon, 01 Jan 0001 00:00:00 +0000

Before you begin

Take the following steps to enable the Kubernetes Engine API:

Visit the Kubernetes Engine page in the Google Cloud Platform Console.
Create or select a project.
Wait for the API and related services to be enabled. This can take several minutes.
Enable billing for your project.

If you are not an existing GCP user, you may be able to enroll for a $300 US Free Trial credit.

Choosing a shell

To complete this quickstart, we can use either Google Cloud Shell or a local shell.

Amazon Elastic Kubernetes Service

Mon, 01 Jan 0001 00:00:00 +0000

Create your EKS Cluster using the Getting Started Guide.

Possible steps are the following:

Create new IAM role for cluster management.
Run aws configure to authorize your awscli with proper AWS Access Key ID and AWS Secret Access Key.
Create an example cluster:

eksctl create cluster \
--name prod \
--version 1.35 \
--nodegroup-name standard-workers \
--node-type t3.medium \
--nodes 3 \
--nodes-min 3 \
--nodes-max 4

Allowing UDP Traffic

For Agones to work correctly, we need to allow UDP traffic to pass through to our EKS cluster worker nodes. To achieve this, we must update the workers’ nodepool SG (Security Group) with the proper rule. A simple way to do that is:

Azure Kubernetes Service

Mon, 01 Jan 0001 00:00:00 +0000

Choosing your shell

You can use either Azure Cloud Shell or install the Azure CLI on your local shell in order to install AKS in your own Azure subscription. Cloud Shell comes preinstalled with az and kubectl utilities whereas you need to install them locally if you want to use your local shell. If you use Windows 10, you can use the WIndows Subsystem for Windows as well.

Creating the AKS cluster

If you are using Azure CLI from your local shell, you need to log in to your Azure account by executing the az login command and following the login procedure.

OCI Kubernetes Engine

Mon, 01 Jan 0001 00:00:00 +0000

Create your OKE Cluster using the Getting Started Guide.

Note

To create a cluster, you must either belong to the tenancy’s Administrators group, or belong to a group to which a policy grants the CLUSTER_MANAGE permission. See Policy Configuration for Cluster Creation and Deployment.

Possible steps to create OKE cluster through OCI web console are the following:

Open the navigation menu and click Developer Services. Under Containers & Artifacts, click Kubernetes Clusters (OKE).
Select the compartment in which you want to create the cluster.
On the Clusters page, click Create cluster.
Select one of the following workflows to create the cluster:
- Quick Create: Select this workflow when you only want to specify those properties that are absolutely essential for cluster creation. When you select this option, Kubernetes Engine uses default values for many cluster properties, and creates new network resources as required.
- Custom Create: Select this workflow when you want to be able to specify all of the cluster’s properties, use existing network resources, and select advanced options.
Click Submit.
Complete the pages of the workflow you selected. For more information, see:
- Using the Console to create a Cluster with Default Settings in the ‘Quick Create’ workflow
- Using the Console to create a Cluster with Explicitly Defined Settings in the ‘Custom Create’ workflow

Allowing UDP Traffic

For Agones to work correctly, we need to allow UDP traffic to pass through to our OKE cluster worker nodes. To achieve this, we must update the workers’ nodepool SG (Security Group) with the proper rule. A simple way to do that is:

Minikube

Mon, 01 Jan 0001 00:00:00 +0000

Installing Minikube

First, install Minikube, which may also require you to install a virtualisation solution, such as VirtualBox as well.

Starting Minikube

Minikube will need to be started with the supported version of Kubernetes that is supported with Agones, via the --kubernetes-version command line flag.

Optionally, we also recommend starting with an agones profile, using -p to keep this cluster separate from any other clusters you may have running with Minikube.

minikube start --kubernetes-version v1.34.6 -p agones

For testing scenarios that require multiple nodes, you can add the --nodes parameter to create a multi-node cluster.