-
Notifications
You must be signed in to change notification settings - Fork 65
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.
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
Upgrade our k8s clusters to k8s 1.26+ #3249
Comments
github-project-automation
bot
moved this to Needs Shaping / Refinement
in DEPRECATED Engineering and Product Backlog
Oct 10, 2023
consideRatio
changed the title
Upgrade our k8s clusters to k8s 1.26+
Upgrade our k8s clusters to k8s 1.25+
Oct 10, 2023
consideRatio
changed the title
Upgrade our k8s clusters to k8s 1.25+
Upgrade our k8s clusters to k8s 1.26+
Oct 10, 2023
consideRatio
moved this from Needs Shaping / Refinement
to Blocked
in DEPRECATED Engineering and Product Backlog
Oct 10, 2023
Just got a notification about ubc-eoas being on 1.24: https://2i2c.freshdesk.com/a/tickets/1092 |
|
This was referenced Nov 13, 2023
github-project-automation
bot
moved this from Blocked
to Complete
in DEPRECATED Engineering and Product Backlog
Nov 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current status
Sorted, filtered to those we need to upgrade as part of this issue, these are:
Action points
These action points assumes we have already upgraded to 1.25+ (#3224), and that instructions for GKE cluster upgrades are available (#3250) already.
Upgrade the EKS clusters currently at 1.25 to the latest available minor versions.
Instructions are available here.
Improve the AWS EKS cluster upgrade docs if needed
Upgrade the GKE clusters currently at 1.25 to the latest available minor versions.
Instructions should by now be available here.
Improve the GCP GKE cluster upgrade docs if neededRelated
The text was updated successfully, but these errors were encountered: