Dave Protasowski
Dave Protasowski
From the GEP-1911 discussion folks seem onboard with using the K8s `appProtocol` as the mechanic to specify upstream protocol. I have yet to rewrite the GEP but I've created an...
I'm splitting out the backend protocol selection from this GEP to https://github.com/kubernetes-sigs/gateway-api/issues/1911 TLS use cases have already been split out here https://github.com/kubernetes-sigs/gateway-api/issues/1897
Curious what folks think about potentially matching on the `scheme` so that you wouldn't need two `HTTPRoute`s for redirects eg. ```yaml apiVersion: gateway.networking.k8s.io/v1alpha2 kind: HTTPRoute metadata: name: http-filter-redirect spec: hostnames:...
Seems like there's an issue already for matching scheme via pseudo headers - https://github.com/kubernetes-sigs/gateway-api/issues/2455 - though that might only work for HTTP/2 ? One thing I'm curious about though is...
> we want to make sure that they are unique within each individual Gateway. A quick example: This seems fairly limited in my opinion. What about other properties in the...
Actually I realize the listeners would have unique `hostname`'s when setting `tls` - so my comment isn't applicable.
Hi - folks just following up
bump @vincepri @alvaroaleman
Seems like prow is broken? /retest
/test pull-controller-tools-test-master