Sunjay Bhatia
Sunjay Bhatia
when we send a configuration update to a fleet of Envoys, they may return an ACK or NACK to signify if the update was accepted Because we heavily validate user...
> I don't quite understand what you mean, accord to [ACK and NACK semantics summary](https://www.envoyproxy.io/docs/envoy/latest/api-docs/xds_protocol.html?highlight=ack#ack-and-nack-semantics-summary) This doesn't have anything in particular to do with the xDS protocol, but rather how...
We're planning on starting up community meetings again soon, with an ad-hoc meeting coming next week or the week after. We will announce it on slack and the community mailing...
We have not yet prioritized implementing this feature, but are very open to community contributions on design and implementation work to get this moving! @adityasundaramurthy-maersk if you have resources to...
We can discuss on this issue or the #contour channel in the Kubernetes slack workspace
> @adityasundaramurthy-maersk @sunjayBhatia, what's the plan about this, we need it too as of yet no-one has contributed a design for this feature so that would be the first step
I would say this is actually intended behavior, since the leader facility is used to ensure status updates to resources are only ever written by a single contour instance at...
Does this still look blocked given the state of https://github.com/kubernetes-sigs/ingress-controller-conformance? (theres some example of running conformance with sonobuoy and kind etc. https://github.com/kubernetes-sigs/ingress-controller-conformance/blob/master/examples/kind/.github/workflows/main.yaml)
Test results from a couple runs: [ingress-conformance-run-1.tar.gz](https://github.com/projectcontour/contour/files/5674899/ingress-conformance-run-1.tar.gz) [ingress-conformance-run-2.tar.gz](https://github.com/projectcontour/contour/files/5675251/ingress-conformance-run-2.tar.gz) Tests fail intermittently with `connection refused`, my guess is that is b/c the address/status on the Ingress object is updated before Envoy...