-
Notifications
You must be signed in to change notification settings - Fork 97
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
Set Accepted condition type on Gateway status #633
Conversation
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.
Update gateway API compatibility doc. Make sure to callout the GatewayReasonGatewayConflict reason and explain that we only support one Gateway
are docs update missing?
@pleshakov I updated the docs |
40cb30e
to
63b6d4d
Compare
e993128
to
72e1ecf
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.
LGTM
The gocyclo linter complained about the complexity of the bindRouteToListeners function. This commit refactors this function to reduce its complexity.
72e1ecf
to
d5ec72b
Compare
Closes #368
Sets Accepted condition type on Gateway status. Accepted can be
true/false
and the following reasons are used:ListenersNotValid
,Invalid
,GatewayConflict
, andAccepted
.The
Invalid
reason is used when the GatewayClass for the Gateway is missing or invalid. In this case, both the Gateway and all its listeners are considered invalid. No additional validation is performed for the listeners. The Gateway and its listeners will have the conditionAccepted/false/Invalid
set on their statuses.This PR also replaces the
ListenerUnsupportedAddress
Condition reason with theListenerUnsupportedValue
reason to be consistent with the rest of our unsupported fields.