Envoy Knowledge

Kip Landergren

(Updated: )

My Envoy knowledge base explaining an overview, the core idea, and key concepts.

Contents#

Overview#

Envoy was born out of a few intertwining needs:

And what was created boils down to:

Core Idea#

Make network transparent to applications.

Key Concepts#

architecture-wise:

big ideas:

here is how it works:

envoy can also be configured as a strict TCP proxy where all TCP traffic is passed through.

On configuration:

Components#

Filters#

Network-Level Filters#

HTTP Filters#

Route Tables#

A component of Filters that matches the route for a filter.

configuration as a service#

evidently envoy can be configured to talk to a configuration service rather than rely on files?

Cluster Manager#

HTTP Connection Manager#

xDS (* Discovery Service)#

Cluster Discovery Service (CDS)#

Service Discovery#

gRPC support#

gRPC-web support#

Terminology#

cluster#
1.

A cluster is a group of logically similar upstream hosts that Envoy connects to. Envoy discovers the members of a cluster via service discovery. It optionally determines the health of cluster members via active health checking. The cluster member that Envoy routes a request to is determined by the load balancing policy.

— https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/intro/terminology

Related:

downstream#
1.

A downstream host connects to Envoy, sends requests, and receives responses.

— https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/intro/terminology

Related:

filter#
1.
filter chain#
1.
front proxy#
1.
HTTP L7 proxy#
1.
host#
1.

An entity capable of network communication (application on a mobile phone, server, etc.). In this documentation a host is a logical network application. A physical piece of hardware could possibly have multiple hosts running on it as long as each of them can be independently addressed.

— https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/intro/terminology

Related:

L3/L4 network proxy#
1.
listener#
1.

A listener is a named network location (e.g., port, unix domain socket, etc.) that can be connected to by downstream clients. Envoy exposes one or more listeners that downstream hosts connect to.

— https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/intro/terminology

Related:

mesh#
1.

A group of hosts that coordinate to provide a consistent network topology. In this documentation, an “Envoy mesh” is a group of Envoy proxies that form a message passing substrate for a distributed system comprised of many different services and application platforms.

— https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/intro/terminology

out of process architecture#
1.
proxy#
1.
runtime configuration#
1.

Out of band realtime configuration system deployed alongside Envoy. Configuration settings can be altered that will affect operation without needing to restart Envoy or change the primary configuration.

— https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/intro/terminology

Also: dynamic configuration

service-oriented architecture#
1.
sidecar#
1.
stunnel#
1.
upstream#
1.

An upstream host receives connections and requests from Envoy and returns responses.

— https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/intro/terminology

Related: