Skip to content

How to easily keep updating agones to the latest version #1742

@axot

Description

@axot

Is your feature request related to a problem? Please describe.
We are thinking about how to introduce agones to our more and more projects.
The problem we're facing now is, k8s has 4 minor upgrade in a single year.
This meaning we have to switch agones k8s cluster to the new one for each time.
If there are 5 projects are using agones this becomes 5x4=20 times a year.
And a single operation to switch all realtime traffic to new cluster also risk and take much operation time.
It will be an almost impossible mission for our limited k8s engineers.

Describe alternatives you've considered
Another thing to consider is, agones is heavily using CRD and custom controller,
this meaning we have to figure out all changes in source code level.
And do integration test for each version.

Describe the solution you'd like
We want to discuss together to find a safer and less costly way to operate.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/operationsInstallation, updating, metrics etcawaiting-maintainerBlock issues from being stale/obsolete/closedkind/designProposal discussing new features / fixes and how they should be implementedkind/featureNew features for Agones

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions