CrossNamespaceObjectReference: Fix MaxLength validation to k8s max 253 char #1108
Conversation
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
… max size of 253 Signed-off-by: Lars Haugan <[email protected]>
matheuscscp
force-pushed
the
fix-crossnamespaceobjectref-maxlength
branch
from
78b30bb to
2284a0d
Compare
matheuscscp
approved these changes
May 27, 2025
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.
CrossNamespaceObjectReference should limit reference names to 253, which is the limit for
.metadata.nameand.metadata.namespace, ref https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names