Validate cluster name using RFC 1123 regexp #1648
Merged
Conversation
This file contains 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
Signed-off-by: Marko Mudrinić <[email protected]>
kubermatic-bot
added
the
release-note
kubermatic-bot
added
dco-signoff: yes
|
LGTM label has been added. Git tree hash: 9e3f6c80b1130a2f6cb25c608c0e13cc970e14f4
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik, xmudrii 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 |
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.
What this PR does / why we need it:
#1641 introduced validation for the cluster name to fix #1630. However, the regexp used in that PR is too restrictive because it doesn't allow dots, which are allowed by RFC 1123. Also, the original implementation doesn't cover other requirements defined by RFC 1123:
This PR uses the regexp used by Kubernetes to validate RFC 1123 subdomains.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):xref #1630
Does this PR introduce a user-facing change?:
/assign @kron4eg @ahmedwaleedmalik