Skip to content

Installing Minikube and Agones Locally

Set up Minikube and Agones locally on Windows 10 or 11 using the Hyper-V driver for Unreal Engine dedicated server development.

Prerequisites

  • Windows 10 or 11 with Hyper-V enabled
  • PowerShell (run as Administrator when required)
  • Chocolatey installed

Enable Hyper-V

If not already enabled, open PowerShell as Administrator:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

Restart your PC when prompted.

Step 1 — Install Minikube

choco install minikube -y

Restart PowerShell, then verify:

minikube version

Step 2 — Start the Minikube Cluster

minikube start --driver=hyperv --disk-size=100g --cpus=2 --memory=6144

Verify the cluster is running:

kubectl get nodes

Kubeconfig is created automatically at %USERPROFILE%\.kube\config.

Step 3 — Install Helm

choco install kubernetes-helm -y

Verify:

helm version

Step 4 — Install Agones

Agones is installed into the Kubernetes cluster, not on your local machine.

helm repo add agones https://agones.dev/chart/stable
helm repo update
helm install agones agones/agones --namespace agones-system --create-namespace

Step 5 — Verify Agones

kubectl get pods -n agones-system -o wide

All of these pods should be in Running state:

  • agones-controller
  • agones-allocator
  • agones-ping
  • agones-webhook

Step 6 — Get KUBE_SERVER, KUBE_TOKEN, and KUBE_CA

The backend needs three values to connect to the Kubernetes API.

Option A — MIP Control Panel (recommended):

Open the Control Panel → set mode to Local → Kubes tab → click 01 Get KUBE Tokens (Minikube).

A Git Bash terminal opens and:

  1. Switches to the minikube context (and switches back afterwards)
  2. Applies the RBAC manifests (serviceaccount.yaml, role.yaml, clusterrole.yaml)
  3. Creates a 10-year ServiceAccount token
  4. Prints KUBE_SERVER, KUBE_TOKEN, and KUBE_CA
  5. Asks for a .env file path — enter the path to your local backend .env and the values are written automatically

Option B — Script directly:

Open Git Bash and run:

cd MIPScripts/kubes/config
bash 02-get-minikube-token.sh

The script behaves the same as Option A.

Note

The script lives at MIPScripts/kubes/config/02-get-minikube-token.sh. It is separate from the remote k3s token script (02-apply-and-get-token.sh) used in Test/Shipping mode.