== Problem ==
We are several years behind kubernetes upgrades, and in order to catch up, we need to upgrade faster than upstream releases for some time.
=== Constraints and risks ===
* All the problems of running old software (security, bugs, stability, ...)
=== Extra info ===
* Current upgrade process documentation - https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin/Kubernetes/Upgrading_Kubernetes
* Latest upgrade task - {T362869} (the rest are subtasks of it)
* Upstream releases - https://kubernetes.io/releases/
== Decision record ==
In progress
https://wikitech.wikimedia.org/wiki/Wikimedia_Cloud_Services_team/EnhancementProposals/Decision_record_T302593_How_do_we_make_decisions
== Options ==
=== Option 1 ===
Do nothing
Pros:
* No extra effort needed
Cons:
* We never catch up
=== Option 2 ===
Create a dedicated opt-in workgroup to focus on monthly Kubernetes upgrades until we catch up, and continue with regular updates thereafter.
Pros:
* K8s upgrade progress greatly improves
* we spread upgrade knowledge in the team
* we setup a working group that can then take over the regular updates (3/year)
* automation improvement and refinement
Cons:
* Considerable effort sometimes when api deprecations happen to affect us
* Are monthly updates compatible with other work streams?
=== Option N ===
Add your options here