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
Bug 1896977: Enhance host name validation in router #238
Bug 1896977: Enhance host name validation in router #238
Conversation
@candita: This pull request references Bugzilla bug 1896977, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions 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/test-infra repository. |
67bc39c
to
e60b47c
Compare
Companion PR in openshift/apiserver: openshift/openshift-apiserver#167 |
/hold for openshift/library-go#975 |
/hold for openshift/api#830 |
e60b47c
to
c9955b4
Compare
c9955b4
to
2d2adc5
Compare
/test e2e-agnostic |
1 similar comment
/test e2e-agnostic |
/retest |
/test e2e-upgrade |
Looks good to me. |
}, | ||
}, | ||
expectedErrors: true, | ||
}, |
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.
Might as well add a couple test cases with the annotation.
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.
I can add some. There are some test cases in the complement PR: https://github.com/openshift/openshift-apiserver/pull/167/files#diff-e571a492e8cca2251f9208e5274c4c9a4e67368113b1b6f131dd5b685c5eaa56
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.
It'd be good to add a test case or two here to get coverage to make sure ValidateHostName
correctly looks up the annotation and passes it to ValidateHost
.
2d2adc5
to
7a106ec
Compare
Thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: candita, Miciah 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 |
/test e2e-agnostic |
/hold cance |
/unhold |
@candita: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with Bugzilla bug 1896977 has not been moved to the MODIFIED state. In response to this:
Instructions 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/test-infra repository. |
Router host name validation did not properly report an issue with a DNS label over length. Update it to use a k8s apimachinery host name validation that reports the issue properly, as well as enforcing host name must have at least two labels (new), with each label less than 63 chars, and total length less than 253 chars. Trailing dots are allowed (new).
Also remove an unneeded/noisy error log in host admitter and correct/add unit tests.