Have Gateway Provisioner give Envoy Service Port protocol hints by setting AppProtocol field #6294
Labels
area/gateway-api
Issues or PRs related to the Gateway (Gateway API working group) API.
area/gateway-provisioner
Issues or PRs related to the Gateway provisioner
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/needs-triage
Indicates that an issue needs to be triaged by a project contributor.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
Please describe the problem you have
For integrations of Gateway API and Contour like knative's
net-gateway-api
, there is no great way right now to know which Envoy Service ports are for which protocols.net-gateway-api
uses these ports to probe Envoy to see when an route is fully ready and serving traffic (of course if we had some of this logic implemented in Contour and were able to do this ourselves, set the right conditions on HTTPRoutes, etc. then this would be moot...).Right now we name Envoy Service ports with the protocol and port number requested by Listeners, e.g.
http-80
for an HTTP Listener on port 80 orhttps-443
for an HTTPS Listener on port 443.net-gateway-api
currently assumes what ports it needs to probe based on the name andAppProtocol
field (see logic here). The logic is somewhat tied to how Istio does things currently.In lieu of a formal way to configure this information recommended by the Gateway API, this seems like what the
AppProtocol
field is designed for. We can offernet-gateway-api
a hint as to which ports are HTTP vs. HTTPS by setting theAppProtocol
field on the Envoy Service port based on the requested Gateway Listener protocol etc.The text was updated successfully, but these errors were encountered: