-
Notifications
You must be signed in to change notification settings - Fork 607
Clarify Gateway Listener Distinct definitions #3477
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
Clarify Gateway Listener Distinct definitions #3477
Conversation
3c5c90c to
5918d70
Compare
Signed-off-by: Nick Young <[email protected]>
5918d70 to
8a2a553
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.
This is a great effort, thanks @youngnick!
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.
Thanks @youngnick! This is a great set of improvements! As I mentioned in today's community meeting, I'll defer on merging this until Friday to give everyone a chance to review.
/hold
| // * The implementation MUST NOT pick one conflicting Listener as the winner. | ||
| // ALL indistinct Listeners must not be accepted for processing. | ||
| // * At least one distinct Listener MUST be present, or else the Gateway effectively | ||
| // contains _no_ Listeners, and must be rejected from processing as a whole. |
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.
This seems like something that would be fairly easy to write a conformance test for. Once this merges, we should file a follow up issue for this.
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.
Agreed.
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.
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mlavacca, robscott, youngnick 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 |
fb2d263 to
19dbede
Compare
19dbede to
29fc5f9
Compare
|
Soak time has passed, will LGTM once the comment above is resolved. /hold cancel |
Signed-off-by: Nick Young <[email protected]>
29fc5f9 to
d29c8dd
Compare
|
/lgtm |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
This PR updates the Listener godocs to clarify:
Updates #3297
Does this PR introduce a user-facing change?: