-
Notifications
You must be signed in to change notification settings - Fork 335
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 Gateway API Gateway
status
#3617
Comments
I was totally wrong on this one. Listener names must be unique within a Gateway, and the CRD has listmap annotations so that the API server enforces that. So it is safe to assume they are unique. |
This PR covers ListenerConditionResolvedRefs (i.e. checking certificate references for ReferencePolicy) and Ready conditions. Part of #3617 Signed-off-by: Mike Beaumont <mjboamail@gmail.com>
This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. |
Part of #3617 Signed-off-by: Mike Beaumont <mjboamail@gmail.com>
Part of #3617 Signed-off-by: Mike Beaumont <mjboamail@gmail.com>
Part of kumahq#3617 Signed-off-by: Mike Beaumont <mjboamail@gmail.com> Signed-off-by: Sally Blich <sally.blich@walkme.com>
Part of kumahq#3617 Signed-off-by: Mike Beaumont <mjboamail@gmail.com> Signed-off-by: Sally Blich <sally.blich@walkme.com>
Description
https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1alpha2.GatewayStatus
Outstanding issues:
Decide how to handle non-unique listener names, see feat(gateway): initial support for GatewayStatus.Listeners #3609 (comment), handled upstream feat(gateway): initial support for GatewayStatus.Listeners #3609 (comment)The text was updated successfully, but these errors were encountered: