Use latest Kubernetes versions for GCP clusters#3182
Merged
Adam-D-Lewis merged 2 commits intomainfrom Nov 11, 2025
Merged
Conversation
dcmcand
approved these changes
Nov 11, 2025
Contributor
dcmcand
left a comment
There was a problem hiding this comment.
🚀 thanks for this @Adam-D-Lewis
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Whenever you go to deploy Nebari again and you've specified a shortened version of the Kubernetes version e.g. "1.31", there's a really painful wait time as all the node groups are switched out. To a lesser extent, some auto applied labels are also deleted and is annoying to wait for. This PR solves those issues.
This PR:
This ensures GCP clusters always use the most recent patch version available for the specified Kubernetes minor version.