-
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
cd: upgrade helm 3.8 -> 3.11 and kubectl 1.23 -> 1.24 #2314
cd: upgrade helm 3.8 -> 3.11 and kubectl 1.23 -> 1.24 #2314
Conversation
Merging this PR will trigger the following deployment actions. Support and Staging deployments
Production deployments
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - appreciate the detailed comments included in the changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as well.
Thanks for the review @pnasrat and @damianavila!! |
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/4357110342 |
K8s 1.25 is out, and we may very well upgrade to it or create a new cluster with it very soon. That makes it relevant to ahead of time upgrade
kubectl
to version 1.24 so that we can assume based on a k8s official version skew poolicy that kubectl can work against the not yet deployed/upgaded k8s 1.25 cluster.I think historically we have been held back by k8s clusters versioned 1.21 or older, but now we are at k8s 1.22 and above so we can probably make this upgrade.
I didn't find the reason why we were still using helm 3.8.2, but I recall issues of using something newer at some point. But with all Helm charts upgraded to modern versions and k8s clusters upgraded to 1.22+ I think we can also upgrade helm at this point.
Related