helm-chart: require k8s 1.29+, up from 1.25+ #846
Merged
Conversation
This file contains 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
consideRatio
changed the title
consideRatio
force-pushed
the
pr/require-k8s-1.29-and-up
branch
from
d25e265 to
b9ffc69
Compare
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.
I'm adopting the same principle as in jupyterhub/zero-to-jupyterhub-k8s, which I think is reasonable - to drop support of k8s versions that are no longer supported by typical cloud providers like GCP/AWS/Azure. In January 2025, k8s 1.28 is too old for those cloud providers. See jupyterhub/zero-to-jupyterhub-k8s#3510 for links with details about this.