/site/docs/installation/ Recent content in Install and configure Agones on Kubernetes on Agones Hugo -- gohugo.io en /site/docs/installation/confirm/ Mon, 01 Jan 0001 00:00:00 +0000 /site/docs/installation/confirm/ To confirm Agones is up and running, run the following command: kubectl describe --namespace agones-system pods It should describe six pods created in the agones-system namespace, with no error messages or status. All Conditions sections should look like this: Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True All this pods should be in a RUNNING state: kubectl get pods --namespace agones-system NAME READY STATUS RESTARTS AGE agones-allocator-5c988b7b8d-cgtbs 1/1 Running 0 8m47s agones-allocator-5c988b7b8d-hhhr5 1/1 Running 0 8m47s agones-allocator-5c988b7b8d-pv577 1/1 Running 0 8m47s agones-controller-7db45966db-56l66 1/1 Running 0 8m44s agones-ping-84c64f6c9d-bdlzh 1/1 Running 0 8m37s agones-ping-84c64f6c9d-sjgzz 1/1 Running 0 8m47s That’s it! /site/docs/installation/upgrading/ Fri, 16 Aug 2019 00:19:19 +0000 /site/docs/installation/upgrading/ Note Whichever approach you take to upgrading Agones, make sure to test it in your development environment before applying it to production. Upgrading Agones The following are strategies for safely upgrading Agones from one version to another. They may require adjustment to your particular game architecture but should provide a solid foundation for updating Agones safely. The recommended approach is to use multiple clusters, such that the upgrade can be tested gradually with production load and easily rolled back if the need arises.