-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Enhance label and taint documentation in kubectl #55274
Enhance label and taint documentation in kubectl #55274
Conversation
/ok-to-test |
@venezia can you squash the commits down to one? otherwise lgtm |
1d8ad20
to
42ffe38
Compare
42ffe38
to
cdd945a
Compare
… clarified both key and value to labels can be 63 characters long
cdd945a
to
53b3b5b
Compare
Done - thanks! |
/lgtm |
/assign @adohe |
/sig cli |
/approve no-issue |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, shiywang, venezia Associated issue requirement bypassed by: deads2k The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue (batch tested with PRs 55648, 55274, 54982, 51955, 55639). If you want to cherry-pick this change to another branch, please follow the instructions here. |
What this PR does / why we need it:
This adds some language around how taint and label keys can have a domain + '/' in front of them. From the current documentation, it would seem like these are not allowed even though well known labels have them.
Also, it seemed unclear (to me) that both the label's key and value can be 63 characters long. I wanted to clarify this.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):None
Special notes for your reviewer:
Phrasing of "DNS subdomain prefix and '/'" was copied from a validator's message ... I'm unsure if its the best wording, but wanted to be consistent with the validator.
Release note: