-
Notifications
You must be signed in to change notification settings - Fork 21
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
Limit upstream-host label value to 43 chars #186
Limit upstream-host label value to 43 chars #186
Conversation
71b5099
to
2f3028a
Compare
2f3028a
to
9baddf4
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.
Minor comments, otherwise lgtm
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.
/lgtm
LGTM label has been added. Git tree hash: 5213db4f1ee16b4d5b50b9b34a5a9bc12d479937
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ialidzhikov The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
How to categorize this PR?
/area quality
/kind enhancement
What this PR does / why we need it:
The value of labels in Kubernetes is limited to 63 chars. The value of the
upstream-host
label is used to construct the registry cache resource names (registry-<escaped-upstream-host-value>
) and for the StatefulSet name the limit is 52 (see #129) . To use a uniform value for both labels and component names, theupstream-host
label value is limited to 43 chars.Currently the remote registry host (
caches[].upstream
) is used forupstream-host
label value. If this value is longer than 43 chars it is transformed to<truncated-upstream>-<hash>
where<truncated-upstream>
is the upstream truncated to 37 char and<hash>
is the first 5 chars ofupstream
SHA256.Which issue(s) this PR fixes:
Part of #3
Special notes for your reviewer:
Release note: