Fix chart install failure for Kubernetes versions with build suffixes#40
Merged
Fix chart install failure for Kubernetes versions with build suffixes#40
Conversation
9e153c9 to
f910bef
Compare
e63080b to
1e1fa2d
Compare
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.
Description
The
kubeVersionconstraint>=1.24.0rejects Kubernetes versions with build suffixes likev1.33.8-eks-3a10415. Helm treats these suffixes as semver pre-release identifiers, which compare as less than the release version. Changing to>=1.24.0-0allows these versions to pass the constraint. This is a no-op for clusters that report clean version strings.Testing
Verified that
>=1.24.0-0accepts both plain versions (1.33.8) and suffixed versions (1.33.8-eks-3a10415), and still correctly rejects versions below 1.24.0.Documentation
No documentation changes needed.