envoyproxy/envoy

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

Open

#865 ouverte le 30 avr. 2017

Voir sur GitHub
 (16 commentaires) (11 réactions) (2 assignés)C++ (5 373 forks)batch import
area/docsbeginnerhelp wanted

Métriques du dépôt

Stars
 (27 997 stars)
Métriques de merge PR
 (Merge moyen 8j) (378 PRs mergées en 30 j)

Description

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.

Guide contributeur