agones | Dedicated Game Server Hosting and Scaling for Multiplayer | Game Engine library

As with many things Jenkins related, to make this work a couple of plugins will be needed, specifically:

• Kubernetes CLI Plugin
• snakeyaml Plugin (this is per the readYaml Jenkins docs)

Assumptions:

• These actions will be run on Linux based containers configured correctly for executing Jenkins builds
• Several required "variables" will be read from the local file system - these may be build artifacts from earlier in a pipeline, or ENV variables, depending on the setup
• Kubernetes service accounts already exist on the clusters with sufficient permissions to perform the tasks
• Credentials for those accounts have been configured in Jenkins
• fleetconfig.yaml is available on the local filesystem and is a complete fleet config similar to the one posed in the question

In order to treat the various fleets differently, some selection criteria will need to be applied based on the name of the fleet itself, then a loop is needed to go through each region etc.

To keep this simple, there will be a basic if statement to select between types (this could easily be expanded), and then a 2 element loop to go loop through more than one region (again easily expandable to more).

This is written as a complete Stage in Jenkins terms, but obviously is not completely executable on its own. It is as close as it can be to an existing, tested, working configuration that has been run multiple times daily for quite some time.

Although this sticks to the example resources, there is no reason it could not be used to modify, create other resources in Kubernetes generally.