Jesus Munoz

A possible solution suggested by @jenshu As outlined [here](https://github.com/grpc/proposal/blob/master/A9-server-side-conn-mgt.md) configuring _MAX_CONNECTION_AGE_ will close the connection after some time and allow the client to re-resolve the destination. I've tested it with...

Falling back to a previous working configuration is what I would expect, similar thing that happens when you create a bad snapshot for the proxies, it is just rejected and...

First of all, good job!! It would be nice if: - the image could have kubectl - it could be invoked like this: - `docker run -v $HOME/.kube/config:/root/.kube/config kostiscodefresh/glooctl:v1.7.3 glooctl...

I agree, created https://github.com/solo-io/gloo/issues/4990 to track that as separate issue

Currently I am using this workaround: `glooctl check 2>&1|grep -v roundTripper`

_Currently it is possible with kubeResourceOverride but it's not convenient considering we havegloo.gatewayProxies.gatewayProxy.affinity as an interface but gloo.gatewayProxies.gatewayProxy.antiAffinity as bool._ To give context about this: https://github.com/solo-io/gloo/blob/v1.8.17/install/helm/gloo/templates/7-gateway-proxy-deployment.yaml#L96 (additionally, maybe we should...