[K8s] Fix validating label keys #5670
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
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.
Previously we have validated for max length of the entire key which is wrong according to k8s spec https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set whereas the key can be split into 2 segments in case of a "/" delimiter. prefix and name. the name is indeed limited to 64 chars while the prefix can be longer and up to 254 chars.
This PR also indicating the key has been truncated in error in case it exceeds the default 64 chars.
https://iguazio.atlassian.net/browse/ML-5872