Docs: Create Kubernetes Cluster

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

Docs: Install Code Blind

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

If you have not yet created a cluster, follow the instructions for the environment where you will be running Code Blind.

Docs: Deploy Kubernetes cluster and install Code Blind using Terraform

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

Prerequisites

Terraform v1.0.8
Access to the the Kubernetes hosting provider you are using (e.g. gcloud, awscli, or az utility installed)
Git

Note

All our Terraform modules and examples use a Helm 3 Module.

The last Code Blind release to include a Helm 2 module was 1.9.0.

Docs: Confirming Code Blind Installation

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

To confirm Code Blind 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!

Now with Code Blind installed, you can utilise its Custom Resource Definitions to create resources of type GameServer, Fleet and more!

What’s next

Go through the Create a Game Server Quickstart

Docs: Upgrading Code Blind and Kubernetes

Fri, 16 Aug 2019 00:19:19 +0000

Note

Whichever approach you take to upgrading Code Blind, make sure to test it in your development environment before applying it to production.

The following are strategies for safely upgrading Code Blind from one version to another. They may require adjustment to your particular game architecture but should provide a solid foundation for updating Code Blind 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.

Warning

Changing Feature Gates within your Code Blind install can constitute an “upgrade” as it may create or remove functionality in the Code Blind installation that may not be forward or backward compatible with installed resources in an existing installation.

We essentially want to transition our GameServer allocations from a cluster with the old version of Code Blind, to a cluster with the upgraded version of Code Blind while ensuring nothing surprising happens during this process.

This also allows easy rollback to the previous infrastructure that we already know to be working in production, with minimal interruptions to player experience.

The following are steps to implement this:

Create a new cluster of the same size or smaller as the current cluster.
Install the new version of Code Blind on the new cluster.
Deploy the same set of Fleets, GameServers and FleetAutoscalers from the old cluster into the new cluster.
With your matchmaker, start sending a small percentage of your matched players’ game sessions to the new cluster.
Assuming everything is working successfully on the new cluster, slowly increase the percentage of matched sessions to the new cluster, until you reach 100%.
Once you are comfortable with the stability of the new cluster with the new Code Blind version, shut down the old cluster.
Congratulations - you have now upgraded to a new version of Code Blind! 👍

If you are upgrading a single cluster, we recommend creating a maintenance window, in which your game goes offline for the period of your upgrade, as there will be a short period in which Code Blind will be non-responsive during the upgrade.

Installation with install.yaml

If you installed Code Blind with install.yaml, then you will need to delete the previous installation of Code Blind before upgrading to the new version, as we need to remove all of Code Blind before installing the new version.

Start your maintenance window.
Delete the current set of Fleets, GameServers and FleetAutoscalers in your cluster.
Make sure to delete the same version of Code Blind that was previously installed, for example: kubectl delete -f https://raw.githubusercontent.com/googleforgames/agones/<old-release-version>/install/yaml/install.yaml
Install Code Blind with install.yaml.
Deploy the same set of Fleets, GameServers and FleetAutoscalers back into the cluster.
Run any other tests to ensure the Code Blind installation is working as expected.
Close your maintenance window.
Congratulations - you have now upgraded to a new version of Code Blind! 👍

Installation with Helm

Helm features capabilities for upgrading to newer versions of Code Blind without having to uninstall Code Blind completely.

For details on how to use Helm for upgrades, see the helm upgrade documentation.

Given the above, the steps for upgrade are simpler:

Start your maintenance window.
Delete the current set of Fleets, GameServers and FleetAutoscalers in your cluster.
Run helm upgrade with the appropriate arguments, such a --version, for your specific upgrade
Deploy the same set of Fleets, GameServers and FleetAutoscalers back into the cluster.
Run any other tests to ensure the Code Blind installation is working as expected.
Close your maintenance window.
Congratulations - you have now upgraded to a new version of Code Blind! 👍

Upgrading Kubernetes

The following are strategies for safely upgrading the underlying Kubernetes cluster from one version to another. They may require adjustment to your particular game architecture but should provide a solid foundation for updating your cluster 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.

Code Blind has multiple supported Kubernetes versions for each version. You can stick with a minor Kubernetes version until it is not supported by Code Blind, but it is recommended to do supported minor (e.g. 1.12.1 ➡ 1.13.2) Kubernetes version upgrades at the same time as a matching Code Blind upgrades.

Patch upgrades (e.g. 1.12.1 ➡ 1.12.3) within the same minor version of Kubernetes can be done at any time.

Multiple Clusters

This process is very similar to the Upgrading Code Blind: Multiple Clusters approach above.

We essentially want to transition our GameServer allocations from a cluster with the old version of Kubernetes, to a cluster with the upgraded version of Kubernetes while ensuring nothing surprising happens during this process.

This also allows easy rollback to the previous infrastructure that we already know to be working in production, with minimal interruptions to player experience.

The following are steps to implement this:

Create a new cluster of the same size or smaller as the current cluster, with the new version of Kubernetes
Install the same version of Code Blind on the new cluster, as you have on the previous cluster.
Deploy the same set of Fleets and/or GameServers from the old cluster into the new cluster.
With your matchmaker, start sending a small percentage of your matched players’ game sessions to the new cluster.
Assuming everything is working successfully on the new cluster, slowly increase the percentage of matched sessions to the new cluster, until you reach 100%.
Once you are comfortable with the stability of the new cluster with the new Kubernetes version, shut down the old cluster.
Congratulations - you have now upgraded to a new version of Kubernetes! 👍

Single Cluster

Start your maintenance window.
Scale your Fleets down to 0 and/or delete your GameServers. This is a good safety measure so there aren’t race conditions between the Code Blind controller being recreated and GameServers being deleted doesn’t occur, and GameServers can end up stuck in erroneous states.
Start and complete your control plane upgrade(s).
Start and complete your node upgrades.
Scale your Fleets back up and/or recreate your GameServers.
Run any other tests to ensure the Code Blind installation is still working as expected.
Close your maintenance window.
Congratulations - you have now upgraded to a new version of Kubernetes! 👍

– Install and configure Code Blind on Kubernetes

Docs: Create Kubernetes Cluster

Docs: Install Code Blind

Docs: Deploy Kubernetes cluster and install Code Blind using Terraform

Prerequisites

Note

Docs: Confirming Code Blind Installation

What’s next

Docs: Upgrading Code Blind and Kubernetes

Note

Upgrading Code Blind

Warning

Upgrading Code Blind: Multiple Clusters

Upgrading Code Blind: Single Cluster

Installation with install.yaml

Installation with Helm

Upgrading Kubernetes

Multiple Clusters

Single Cluster