Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document a k8s upgrade policy: ensure to always use one of the latest 5 minor versions #3248

Closed
Tracked by #3469
consideRatio opened this issue Oct 10, 2023 · 0 comments · Fixed by #3511
Closed
Tracked by #3469

Document a k8s upgrade policy: ensure to always use one of the latest 5 minor versions #3248

consideRatio opened this issue Oct 10, 2023 · 0 comments · Fixed by #3511
Assignees
@GeorgianaElena
Labels
nominated-to-be-resolved-during-q4-2023 Nomination to be resolved during q4 goal of reducing the technical debt

Comments

@consideRatio
Copy link
Contributor

consideRatio commented Oct 10, 2023 •
edited
Loading

k8s upgrade policy proposal

  1. I propose that we establish a k8s upgrade policy by documenting it here in our docs.
  2. I propose that the format of our k8s upgrade policy initially is to ensure we use a k8s version (in api-plane and nodes) that is at least X minor versions from the latest available at any given time.
  3. I propose that we pick X to be 5 initially, and then raise the ambition in the future to make it 4.
    Currently with k8s 1.28 being the latest minor and 1.29 being released in december 2023, a X=5 policy means we should already have our clusters versioned 1.28, 1.27, 1.26, 1.25, or 1.24. We actually comply with this policy for the moment!

Related
@consideRatio consideRatio moved this from Needs Shaping / Refinement to Ready to work in DEPRECATED Engineering and Product Backlog Oct 10, 2023
@consideRatio consideRatio added the nominated-to-be-resolved-during-q4-2023 Nomination to be resolved during q4 goal of reducing the technical debt label Oct 12, 2023
@GeorgianaElena GeorgianaElena mentioned this issue Nov 2, 2023
Closed
4 tasks
@GeorgianaElena GeorgianaElena mentioned this issue Nov 28, 2023
Closed
@GeorgianaElena GeorgianaElena self-assigned this Nov 30, 2023
@GeorgianaElena GeorgianaElena moved this to Todo 👍 in Sprint Board Nov 30, 2023
@GeorgianaElena GeorgianaElena mentioned this issue Dec 7, 2023
Merged
@github-project-automation github-project-automation bot moved this from Todo 👍 to Done 🎉 in Sprint Board Dec 7, 2023
@github-project-automation github-project-automation bot moved this from Ready to work to Complete in DEPRECATED Engineering and Product Backlog Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@GeorgianaElena GeorgianaElena

Labels
nominated-to-be-resolved-during-q4-2023 Nomination to be resolved during q4 goal of reducing the technical debt
Projects
No open projects
DEPRECATED Engineering and Product Backlog
Status: Complete
Sprint Board
Status: Done 🎉
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add a short initial policy about k8s version used in our clusters GeorgianaElena/pilot-hubs
2 participants
@consideRatio @GeorgianaElena