-
Notifications
You must be signed in to change notification settings - Fork 2.7k
feat(gateway-api): add ability to override target on *Route resources #5319
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
base: master
Are you sure you want to change the base?
feat(gateway-api): add ability to override target on *Route resources #5319
Conversation
Signed-off-by: David van der Spek <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @davidspek. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
docs/sources/gateway.md
Outdated
1. If a matching parent Gateway has the `external-dns.alpha.kubernetes.io/target` annotation, uses | ||
the values from that unless the route has the `external-dns.alpha.kubernetes.io/target: ""` annotation in which case it iterates over that parent Gateway's `status.addresses` adding each address's `value`. | ||
|
||
2. Otherwise, iterates over that parent Gateway's `status.addresses`, | ||
2. If the route has the route has the `external-dns.alpha.kubernetes.io/target` annotation with a non-empty value, uses the value from that. | ||
|
||
3. Otherwise, iterates over that parent Gateway's `status.addresses`, |
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.
If target annotation apply first, would you please re-order it ?
It should simplify the wording
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 for the suggestion. I've updated the docs.
/ok-to-test |
Signed-off-by: David van der Spek <[email protected]>
Co-authored-by: Michel Loiseleur <[email protected]>
Co-authored-by: Michel Loiseleur <[email protected]>
/retest |
Description
This PR adds the ability to use the
external-dns.alpha.kubernetes.io/target
annotation on *Route (like HTTPRoute) resources to override the target coming from the Gateway. A special case is included where if the gateway also includes theexternal-dns.alpha.kubernetes.io/target
annotation and the *Route has theexternal-dns.alpha.kubernetes.io/target
set to""
the target annotation from the Gateway isn't used and the normal flow gathering the listener address from the gateway is used.Fixes #4779
Checklist