Envoy: Minimal gRPC service-to-service config example with health checking

[egoldschmidt]

Envoy is impressive, and its documentation is far-reaching, but the wealth of configuration options means its difficult to know if you're setting things up right. In my case, all I want is automatic health-check driven connection draining to ensure zero-downtime deploys. Yet after setting up an SDS server, health check listeners, retry policies, and more I still see requests being forwarded to Envoy servers that are returning 503's.

Has anyone put together a minimal configuration example that provides what I'm looking for? I know that gRPC is a bit of a special case but I suspect many folks would love something simple to start with, as opposed to the extremely complex configs on the documentation website.

I should note that I'm running Envoy on both the client and server.

[mattklein123]

We would like to have more examples, but unfortunately don't have resources to have someone work on refining all of the getting started/example documentation. Will leave this open to track us doing it at some point or perhaps someone contributing an example. In the meantime, we can help you debug on Gitter if you ask questions there.

[fabianfett]

@egoldschmidt Have you found anything? How did you solve your problem?

[philbour]

Has anyone got anywhere with this?

[arkadyb]

Were you able to get something to work? Im trying to build grpc service mesh.

[cmluciano]

Any chance we can enhance the grpc bridge example to satisfy this issue?

[mattklein123]

@cmluciano optimally it would be a pure gRPC example IMO.

[dio]

I have a (too) simple setup example here: https://github.com/dio/simple-grpc will add xDS (probably CDS first) in the mix. After some cleanups, I'll try to submit a PR.

[srikailash]

@mattklein123, feel free to assign this to me.

[dio]

cc. @phlax