James Peach

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

I spent some time replicating this. I spun up a 4 node cluster on GKE with [this script](https://github.com/jpeach/kustomize/blob/master/hack/gke-make-cluster.sh). My backend service was [this echo server](https://github.com/kubernetes-sigs/ingress-controller-conformance/blob/master/tools/echoserver.go), which `ab` can drive at...

In principle, I think that exposing envoy's information about clusters is a good idea. It's useful for regular services and also for special infrastructure services.

Note to self: General envoy cluster metrics that could be used to support this feature: Name | Type | Desc -- | -- | -- membership_healthy | Gauge | Current...

https://istio.io/blog/2020/deploy-wasm-declarative/ https://istio.io/docs/concepts/wasm/

Seems closely related to https://github.com/projectcontour/contour/issues/3006

Note that this doesn't solve configuration snapshot consistency issues (see various issues in the go-control-plane repo).

Seems related to Multi-Cluster Services API proposal presented to sig-network https://docs.google.com/document/d/1hFtp8X7dzVS-JbfA5xuPvI_DNISctEbJSorFnY-nz6o

Should this still be in the prioritized backlog? It seems like a research project that needs scoping.

> we can leave it there for now. there are asks on this from users Can you please add links to those?