feat: enforce 63-character limit on resource names#348
feat: enforce 63-character limit on resource names#348chw120 wants to merge 2 commits intokubernetes-sigs:mainfrom
Conversation
|
Welcome @chw120! |
|
Hi @chw120. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
✅ Deploy Preview for agent-sandbox canceled.
|
janetkuo
left a comment
There was a problem hiding this comment.
Please hold off this change, see #342 (comment)
igooch
left a comment
There was a problem hiding this comment.
LGTM.
As an interesting finding, I tested this with "generateName" for the SandboxClaim, and at main the extra long name prefix was not truncated and had the expected 5 unique characters appended to the name. For this PR it truncated the name prefix to the first 58 characters of the name, and still added on the unique 5 characters for a total name of 63 characters.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: chw120, igooch The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
There was a problem hiding this comment.
/lgtm
ETA: My bad, just saw @janetkuo's above comment to hold off on this one
|
/hold |
Fixes #342