-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add length limits to API name #602
base: main
Are you sure you want to change the base?
add length limits to API name #602
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for kurator-dev canceled.
|
462df79
to
f843110
Compare
f843110
to
6348727
Compare
name := customCluster.Name + "-" + ClusterHostsName | ||
name = strings.ToLower(name) | ||
if len(name) > 63 { | ||
name = name[:63] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two cents:
- donot hardcode
- If we strip, could we get duplicate resource names?
Signed-off-by: LiZhenCheng9527 <lizhencheng6@huawei.com>
6348727
to
141b1fd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
iirc, this is not right, if the name is suffixed with random chars, when we reconcile delete, we could not cleanup the generated resources
What type of PR is this?
/kind feature
Which issue(s) this PR fixes:
a part of #544