Open Andrei-Predoiu opened 5 months ago
Actually its already possible to use these annotations in a gateway. Just try it you will be surprised. Not sure when they added that. And its also not documented anywhere, at least I just have found what you wrote above. And whats also not documented it that you need to add the httproute and the tlsroute as sources either in a args/cmd field or in a helm chart.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
My team has ran an experimental migration of our k8s platform from ingress to gateway api. external-dns is one of the key areas we had issues in.
What would you like to be added:
Currently external-dns is implemented to use the
HttpRoute
resource to provision DNS. I suggest moving the annotation support to theGateway
resource instead.Why is this needed:
HttpRoute
resource is meant to be used by app devs, while the DNS of the gateway falls more in theClusterOperator
role.HttpRoutes
but it's not what the gateway was designed to do. I would suggest that individuals with this use case either useingress
, configure multiple gateway instances, or use route filters/rules.Gateway
orGatewayClass
resources are the ones that have the actual external IP of the gateway, definitely not theHttpRoute
. In our experiment, the IP detected by external-dns was wrong. (I forgot to write down exactly where the real IP was, sorry)external-dns
. They annotate theGateway
resource, thus these tools don't really work the same way any more in the Gateway API realm