-
Notifications
You must be signed in to change notification settings - Fork 95
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
Update k8s max version #2903
Update k8s max version #2903
Conversation
…inor versions, and upgrade k8s and helm terraform providers
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.
Thanks @dcmcand, changes look good! 🚀
You tested this on the three cloud providers and it worked on all of them, so I'm approving the PR.
However, I ran the cloud integration tests from this branch, and AWS is failing but I haven't checked why that is. It might not be related with these changes as I saw it failed from another branch too but I haven't checked whether the errors are the same. We can double check before merging this PR
@dcmcand I'm running into different issues when testing on AWS. Deploying from scratchWhen deploying from scratch using: amazon_web_services:
kubernetes_version: '1.31'
... I'm getting the following error during the deployment:
It seems to be the same error in the AWS integration tests I ran from this branch. Upgrading an existing clusterI successfully deployed Nebari using: amazon_web_services:
kubernetes_version: '1.29'
... I then changed it to: amazon_web_services:
kubernetes_version: '1.30'
... and when re-deploying, ran into:
Regardless, I went to the EKS console and upgraded the node groups manually, as outlined in https://www.nebari.dev/docs/how-tos/kubernetes-version-upgrade/ Then, I updated the config to: amazon_web_services:
kubernetes_version: '1.31'
... and when re-deploying, I ran into:
I had to manually upgrade the node groups again, and only after that, keycloak was accessible. |
For some reason the PV for the ingress cert isn't being created. |
https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions-standard.html |
@marcelovilla aws deploy worked with 1.31 for me locally and deployment test now passes https://github.com/nebari-dev/nebari/actions/runs/12810668708/job/35718247163. Do you want to retest before I merge? |
Nice find @dcmcand! I'm fine with merging it now |
Reference Issues or PRs
closes #2870
What does this implement/fix?
Ups the max kubernetes version to
1.31
which is the highest version that cloud providers currently support.Upgrades the terraform kubernetes provider
Changes the max kubernetes version to use Major and Minor versions instead of Major, Minor, Patch.
Put a
x
in the boxes that applyTesting
How to test this PR?
Deploy to one of the cloud providers using a kubernetes version of
1.29
(the previous max version).Change your kubernetes version to
1.30
and redeployChange your kubernetes version to
1.31
and redeployTest functionality.
Any other comments?