Deployment types

Envoy is usable in a variety of different scenarios, however it’s most useful when deployed as a mesh across all hosts in an infrastructure or as a Kubernetes Ingress Gateway. This section describes three recommended deployment types in increasing order of complexity.

• Service to service only
  • Service to service egress listener
  • Service to service ingress listener
  • Optional external service egress listeners
  • Discovery service integration
  • Configuration template
• Service to service plus front proxy
  • Configuration template
• Service to service, front proxy, and double proxy
  • Configuration template