Can we link any resources we already have (automations, cookbooks, instructions, etc) on how we handle k8s upgrade here too? k8s upgrade is easy on paper but I assume it'll probably be more hairy for our particular implementation. Btw for the decision request I'm going with Option 2

one of the resources we need to be aware of here https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin/Kubernetes/Upgrading_Kubernetes

In T363683#9790665, @Raymond_Ndibe wrote:

one of the resources we need to be aware of here https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin/Kubernetes/Upgrading_Kubernetes

Added it :), feel free to edit the task and add more if you find more

Option 2 seems to me like the obviously good choice :)

On a first read, I was under the impression that the working group would exist only until we catch up, but from option 2 it seems clear that this would become a regular working group.

In T363683#9791133, @Slst2020 wrote:

Option 2 seems to me like the obviously good choice :)

On a first read, I was under the impression that the working group would exist only until we catch up, but from option 2 it seems clear that this would become a regular working group.

Feel free to reword/clarify there :)
Without the long-term workgroup might be another option too if you prefer.

I would like to participate on the upgrades. I don't have any strong opinion on the different options at the moment.

Option 2 (including the long-term workgroup) looks fine to me.

Maybe I would add that "monthly" is the target, but some difficult upgrades might need more time. We could publish a roadmap and highlight the upgrades that we anticipate might require more time, because of API deprecations.

In T363683#9826430, @fnegri wrote:

Option 2 (including the long-term workgroup) looks fine to me.

Maybe I would add that "monthly" is the target, but some difficult upgrades might need more time. We could publish a roadmap and highlight the upgrades that we anticipate might require more time, because of API deprecations.

Sounds good to me, iirc usually there's one big upgrade a year where they deprecate many things/do big changes, I think though that we can keep track of that on the tasks (https://phabricator.wikimedia.org/T316107), after assigning say three of them, the asignees can start looking into what changes come with that upgrade and plan a bit ahead, wdyt? (this can be discussed after, no need to decide now).

I think though that we can keep track of that on the tasks

The task is good to discuss the details, but I see a value in having a high-level wiki page with the list of upgrades, and a very short summary like "this one should be easy", or "this one is complicated, see details in the task".