John Howard
John Howard
If there is a conflict k8s picks one of them to "win" when you type `kubectl get ef`. I am not sure how it picks, it seems `kubectl get gateway`...
We aren't removing it, just hiding it On Mon, Jun 6, 2022 at 6:17 AM Lin Sun ***@***.***> wrote: > Do we need a release note for this in case...
cc @douglas-reid @kyessenov
cc @mandarjog @gargnupur
> I don't have as much experience with http/2 so I have no comment on whether this might affect those clients. I think per the HTTP2 spec servers are expected...
I mentioned this elsewhere but IMO application TLS and mesh encryption (which is not always tls...) should be kept entirely separated
Without thinking too much about the implications, I am thinking yes? But it may be helpful to have the user specify intent here, as adding HTTP3 on the listener may...
FYI https://github.com/istio/istio/wiki/Experimental-QUIC-and-HTTP-3-support-in-Istio-gateways also supports it. I think you could get it working with gateway-api today as well, but its not currently documented (more of a coincidence that it would work...
The tricky thing with HTTP3 IMO is that its on a completely different protocol (UDP). This implies opening 2 ports (not supported in many cases), alt-svc for negotiation, etc. Its...
While I agree with your points, IMO creationTimestamp is useful since it means that new reasources do not break existing ones. That mean if I introduce a conflict, I don't...