Page MenuHomePhabricator
Create Task
Maniphest T363683

Decision request - kubernetes upgrade workgroup
Open, Needs TriagePublic
Actions

Description

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

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

Related Objects

Event Timeline

dcaro created this task.Mon, Apr 29, 10:40 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMon, Apr 29, 10:40 AM
dcaro mentioned this in T362872: Decision Request - Toolforge policy agent enforcement model.Mon, Apr 29, 10:43 AM
fnegri subscribed.Mon, Apr 29, 12:35 PM
fnegri renamed this task from Decision request template - kubernetes upgrade workgroup to Decision request - kubernetes upgrade workgroup.Mon, Apr 29, 5:30 PM
fnegri moved this task from Inbox to Discussion on the Cloud Services Proposals board.
Slst2020 subscribed.Tue, Apr 30, 11:45 AM
dcaro mentioned this in T362233: Decision Request - Toolforge policy agent.Tue, Apr 30, 12:37 PM
Raymond_Ndibe subscribed.Mon, May 13, 2:49 PM
Raymond_Ndibe added a comment.Mon, May 13, 3:07 PM

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

Raymond_Ndibe added a comment.Mon, May 13, 3:09 PM

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

dcaro updated the task description. (Show Details)Mon, May 13, 4:15 PM
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

Slst2020 added a comment.Mon, May 13, 4:30 PM

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.

dcaro added a comment.Mon, May 13, 4:35 PM
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.

Slst2020 updated the task description. (Show Details)Tue, May 14, 7:05 AM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL