Steve Kriss

https://projectcontour.io/docs/1.26/troubleshooting/envoy-container-draining/ has some suggestions that may help

https://github.com/projectcontour/contour/issues/4540 may be at play here

Looks like there are a few things we need to do to get this test passing: 1. in the test suite setup, set UsableNetworkAddresses and UnusableNetworkAddresses a. `UsableNetworkAddresses` must contain...

My initial hunch is that the two different Gateways are both processing the HTTPProxy. This could be avoided by specifying an ingress class for one or the other, and specifying...

The other possibility is that the actual `ContourConfiguration` CRD does not have `enableExternalNameService: true`. This could happen if, when the Gateway was created, the GatewayClass's parameters did not include this...

If you delete the ContourConfiguration CR it should be recreated the next time the Gateway is reconciled (on change, on provisioner restart, etc), but per the Gateway API spec it's...

I came up with https://gist.github.com/skriss/ae3835b964d8ba9477459a2b45c30c8d which seems to work as expected. There is one Gateway that does not support ExternalName services and does not specify an ingress class, a second...

xref https://github.com/projectcontour/contour/issues/2893

I'll take a crack at this now that we've updated to v1alpha2.

This will probably become a conformance issue at some point, but for now, removing from the 1.22 milestone, still open to a contributor picking this up though!