服务网格代理Envoy入门

我就是我 2023-06-27 12:58 44阅读 0赞

# **目录** #

目录 1

1. 前言 2

1.1. Envoy是什么 2

1.2. 如何入门Envoy 2

1.3. Envoy的源码在哪 2

2. 缩略语 3

3. Envoy架构 3

3.1. 外部架构 3

3.2. 内部架构 4

4. Envoy配置文件 5

4.1. admin 5

4.2. static\_resources 6

4.2.1. listeners 6

4.2.2. clusters 6

4.3. dynamic\_resources 8

4.3.1. 怎么理解 8

4.3.2. 全动态配置 8

4.3.3. gRPC接口 9

4.3.4. REST接口 10

5. 试跑体验 10

5.1. 体验目标 10

5.2. 下载Envoy镜像 10

5.3. 准备Envoy配置文件 10

5.4. 启动Envoy容器 12

5.5. 启动Envoy进程 12

5.6. 体验效果 13

6. 动态配置 13

6.1. 动态配置EDS 13

6.1.1. Envoy配置文件 13

6.1.2. EDS服务源码 15

6.1.3. 启动EDS进程 17

6.1.4. 启动Envoy进程 18

1.   **前言**

Envoy入门并不简单，可以说有些陡峭，本文尽可能帮助降低入门门槛。本文内容主要基于[Envoy-1.12.2][]版本，官方链接：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> <a href="https://www.envoyproxy.io/docs/envoy/v1.12.2/configuration/overview/v2_overview" rel="nofollow">https://www.envoyproxy.io/docs/envoy/v1.12.2/configuration/overview/v2_overview</a> </td> 
 </tr> 
 </tbody> 
</table>

1.  1.   **Envoy是什么**

[Envoy][]是Lyft开源的一个C++实现的代理（Proxy），和Nginx及HAProxy类似，可代理L3/L4层和L7层。代理是它最核心和基础的功能，它也是服务网格框架[Istio][]的Sidecar。

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy_size_16_color_FFFFFF_t_70][]

1.  1.   **如何入门Envoy**

从研究Envoy的配置文件开始，Envoy支持多种格式的配置文件：YAML、JSON和PB等，其中YAML使用最多，官方示例基本都是YAML格式的。

配置文件中涉及多个概念，所以最好先将概念了解清楚，然后使用最简单的配置走一遍流程，如果会用Docker则这一步会比较简单。在了解概念之前，最好先了解Envoy的基本架构，以弄明白各概念间的协作关系。

1.  1.   **Envoy的源码在哪**

Envoy的源码托管在Github上：[https://github.com/envoyproxy/envoy][https_github.com_envoyproxy_envoy]。

1.   **缩略语**

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> 缩写 </td> 
 <td style="vertical-align:top;width:137.4pt;"> 全写 </td> 
 <td style="vertical-align:top;width:233.75pt;"> 说明 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> lb </td> 
 <td style="vertical-align:top;width:137.4pt;"> load balance </td> 
 <td style="vertical-align:top;width:233.75pt;"> 负载均衡 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> lb_policy </td> 
 <td style="vertical-align:top;width:137.4pt;"> load balance policy </td> 
 <td style="vertical-align:top;width:233.75pt;"> 负载均衡策略 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> SNI </td> 
 <td style="vertical-align:top;width:137.4pt;"> Server Name Indication </td> 
 <td style="vertical-align:top;width:233.75pt;"> TLS的扩展，用来解决一个服务器拥有多个域名或证书。 工作原理：在连接到服务器建立SSL链接前，先发送要访问的域名，服务器根据这个域名返回一个合适的证书。 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> TLS </td> 
 <td style="vertical-align:top;width:137.4pt;"> Transport Layer Security </td> 
 <td style="vertical-align:top;width:233.75pt;"> 传输层安全性协议 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> L3 </td> 
 <td style="vertical-align:top;width:137.4pt;"> Layer 3 </td> 
 <td style="vertical-align:top;width:233.75pt;"> 网络层（IP） </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> L4 </td> 
 <td style="vertical-align:top;width:137.4pt;"> Layer 4 </td> 
 <td style="vertical-align:top;width:233.75pt;"> 传输层（PORT） </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> L7 </td> 
 <td style="vertical-align:top;width:137.4pt;"> Layer 7 </td> 
 <td style="vertical-align:top;width:233.75pt;"> 应用层（HTTP） </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> L2 </td> 
 <td style="vertical-align:top;width:137.4pt;"> Layer 2 </td> 
 <td style="vertical-align:top;width:233.75pt;"> 数据链路层（MAC） </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> YAML </td> 
 <td style="vertical-align:top;width:137.4pt;"> YAML Ain't a Markup Language </td> 
 <td style="vertical-align:top;width:233.75pt;"> 以数据做为中心的标记语（Yet Another Markup Language） </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> JSON </td> 
 <td style="vertical-align:top;width:137.4pt;"> JavaScript Object Notation </td> 
 <td style="vertical-align:top;width:233.75pt;"> JS 对象简谱，一种轻量级的数据交换格式 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> REST </td> 
 <td style="vertical-align:top;width:137.4pt;"> Representational State Transfer </td> 
 <td style="vertical-align:top;width:233.75pt;"> 表述性状态传递，一种软件架构风格 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> gRPC </td> 
 <td style="vertical-align:top;width:137.4pt;"> Google RPC </td> 
 <td style="vertical-align:top;width:233.75pt;"> 谷歌开源的RPC框架 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> pb </td> 
 <td style="vertical-align:top;width:137.4pt;"> Protocol buffers </td> 
 <td style="vertical-align:top;width:233.75pt;"> 谷歌开发的一种数据描述语言，常被简称为protobuf </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:54.95pt;"> Endpoint </td> 
 <td style="vertical-align:top;width:137.4pt;"> &nbsp; </td> 
 <td style="vertical-align:top;width:233.75pt;"> 可理解为IP端口对，每个服务需要配置一个Endpoint </td> 
 </tr> 
 </tbody> 
</table>

1.   **Envoy架构**
    
    1.   **外部架构**

下图展示了Envoy的外部架构，从图很容易看到服务间、应用和服务间都是通过Envoy串联起来的，Envoy是它们间的高速公路，Envoy的作用就是在各部分间转发读写请求（也可叫读写操作），所以Envoy是名副其实的代理（Proxy）。

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy_size_16_color_FFFFFF_t_70 1][]

1.  1.   **内部架构**

外部架构展示了Envoy的作用，但无法窥见它是如何实现的，Envoy的内部结构展示出了它的实现原理。

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy_size_16_color_FFFFFF_t_70 2][]

其中过滤器（Filter）是Envoy的核心中的核心，多Filter形成了过滤器链（Chain），和iptables的Chain类似，请求经过过滤器链后到达目的服务（Service）。

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy_size_16_color_FFFFFF_t_70 3][]

如果将Envoy看成黑盒，则它所处位置可定义成如下图所示：

![20200107103432814.jpg][]

1.   **Envoy配置文件**

对Envoy架构有初步了解后，再通过对Enovy配置文件的了解，将对掌握Enovy十分有帮助。Envoy的配置文件定义了代理转发规则，规则也可通过gRPC或REST动态拉取。

Envoy配置文件支持四种书写格式：json、yaml、pb和pb\_text，官方文档和示例基本使用yaml格式。可将Envoy配置文件分解成三大部分：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> admin </td> 
 <td style="vertical-align:top;width:289.55pt;"> 定义Envoy进程的管理端口 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> static_resources </td> 
 <td style="vertical-align:top;width:289.55pt;"> 静态配置，定义静态资源 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> dynamic_resources </td> 
 <td style="vertical-align:top;width:289.55pt;"> 态配置，定义动态资源，static_resources中一些配置可通过服务调用（接口调用）动态拉取。 </td> 
 </tr> 
 </tbody> 
</table>

1.  1.   **admin**

管理配置，比较简单，内容一般如下：

通过admin可以查询到大量的配置、监控和运维等数据：

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy_size_16_color_FFFFFF_t_70 4][]

1.  1.   **static\_resources**

static\_resources又可分解为两大部分：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> listeners </td> 
 <td style="vertical-align:top;width:289.55pt;"> 定义监听器，服务下游（downstream） </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> clusters </td> 
 <td style="vertical-align:top;width:289.55pt;"> 定义上游（upstream）的微服务集群 </td> 
 </tr> 
 </tbody> 
</table>

1.  1.  1.   **listeners**

在listeners中，可以定义多个listener，每个listener由三部分组成：

1.  1.  1.   **clusters**

定义上游集群，Envoy最基础的功能即是将来自下游的请求转发给上游。clusters的内容包括五大部分，其中**load\_assignment**部分是核心：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> name </td> 
 <td style="vertical-align:top;width:289.55pt;"> 下游集群名，可定义一或多个 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> connect_timeout </td> 
 <td style="vertical-align:top;width:289.55pt;"> 连接上游的超时时长，可带单位，如“0.25s”表示250毫秒 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> type </td> 
 <td style="vertical-align:top;width:289.55pt;"> 集群类型，如STATIC、STRICT_DNS、LOGICAL_DNS和EDS等 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> lb_policy </td> 
 <td style="vertical-align:top;width:289.55pt;"> 负载均衡策略，如ROUND_ROBIN表示轮询 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> load_assignment </td> 
 <td style="vertical-align:top;width:289.55pt;"> type为STATIC、STRICT_DNS和LOGICAL_DNS时，如果type为EDS则使用eds_cluster_config </td> 
 </tr> 
 </tbody> 
</table>

lb\_policy可取值：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> ROUND_ROBIN </td> 
 <td style="vertical-align:top;width:289.55pt;"> 轮询 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> LEAST_REQUEST </td> 
 <td style="vertical-align:top;width:289.55pt;"> 请求最少 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> RING_HASH </td> 
 <td style="vertical-align:top;width:289.55pt;"> 环形哈希 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> RANDOM </td> 
 <td style="vertical-align:top;width:289.55pt;"> 随机 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> MAGLEV </td> 
 <td style="vertical-align:top;width:289.55pt;"> 一致性哈希算法 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:136.55pt;"> CLUSTER_PROVIDED </td> 
 <td style="vertical-align:top;width:289.55pt;"> 定制 </td> 
 </tr> 
 </tbody> 
</table>

**load\_assignment**示例:

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> load_assignment: &nbsp;&nbsp;cluster_name:&nbsp;some_service &nbsp;&nbsp;endpoints: &nbsp;&nbsp;- lb_endpoints: &nbsp;&nbsp;&nbsp;&nbsp;- endpoint: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;socket_address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: 127.0.0.1 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;port_value: 1234 </td> 
 </tr> 
 </tbody> 
</table>

**clusters**示例:

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> clusters: - name: some_service &nbsp;&nbsp;connect_timeout: 0.25s &nbsp;&nbsp;type: STATIC &nbsp;&nbsp;lb_policy: ROUND_ROBIN &nbsp;&nbsp;load_assignment: &nbsp;&nbsp;&nbsp;&nbsp;cluster_name: some_service &nbsp;&nbsp;&nbsp;&nbsp;endpoints: &nbsp;&nbsp;&nbsp;&nbsp;- lb_endpoints: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- endpoint: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;socket_address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: 127.0.0.1 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;port_value: 1234 </td> 
 </tr> 
 </tbody> 
</table>

1.  1.   **dynamic\_resources**

static\_resources中的四种动态资源可通过动态服务发现（**xDS**）来动态配置，共有六种动态服务发现：

<table style="width:426.2pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:36.95pt;"> 缩写 </td> 
 <td style="vertical-align:top;width:144pt;"> 全写 </td> 
 <td style="vertical-align:top;width:245.25pt;"> 说明 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:36.95pt;"> LDS </td> 
 <td style="vertical-align:top;width:144pt;"> Listener&nbsp;Discovery Service </td> 
 <td style="vertical-align:top;width:245.25pt;"> 监听器（资源）发现服务，解决有哪些监听器问题 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:36.95pt;"> CDS </td> 
 <td style="vertical-align:top;width:144pt;"> Cluster&nbsp;Discovery Service </td> 
 <td style="vertical-align:top;width:245.25pt;"> 集群（资源）发现服务，解决有哪些集群问题 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:36.95pt;"> RDS </td> 
 <td style="vertical-align:top;width:144pt;"> Route&nbsp;Discovery Service </td> 
 <td style="vertical-align:top;width:245.25pt;"> 路由（资源）发现服务，解决有哪些路由规则问题 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:36.95pt;"> EDS </td> 
 <td style="vertical-align:top;width:144pt;"> Endpoint&nbsp;Discovery Service </td> 
 <td style="vertical-align:top;width:245.25pt;"> 端点（资源）发现服务，解决集群内有哪些端点问题 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:36.95pt;"> ADS </td> 
 <td style="vertical-align:top;width:144pt;"> Aggregated&nbsp;Discovery Service </td> 
 <td style="vertical-align:top;width:245.25pt;"> 这并不是一个独立的发现服务，而是对其它发现服务的聚合 </td> 
 </tr> 
 </tbody> 
</table>

动态配置在启动Envoy进程时，需要指定id和cluster，否则报错“node 'id' and 'cluster' are required.”。

1.  1.  1.   **怎么理解**

怎么理解dynamic\_resources？在static\_resouces基础上，动态拉取动态资源，即有动态资源配置不是直接写在配置中，而是需要通过服务调用动态取得，Envoy支持gRPC/HTTP2和REST两种方式动态拉取。

1.  1.  1.   **全动态配置**

可以部分动态配置，也可全动态配置。下列为一个官方的全动态配置示例：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> admin: &nbsp;&nbsp;access_log_path: /tmp/admin_access.log &nbsp;&nbsp;address: &nbsp;&nbsp;&nbsp;&nbsp;socket_address: { address: 127.0.0.1, port_value: 9901 } &nbsp; dynamic_resources: &nbsp;&nbsp;lds_config: &nbsp;&nbsp;&nbsp;&nbsp;api_config_source: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;api_type: GRPC &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;grpc_services: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;envoy_grpc: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cluster_name: xds_cluster &nbsp;&nbsp;cds_config: &nbsp;&nbsp;&nbsp;&nbsp;api_config_source: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;api_type: GRPC &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;grpc_services: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;envoy_grpc: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cluster_name: xds_cluster &nbsp; static_resources: &nbsp;&nbsp;clusters: &nbsp;&nbsp;- name: xds_cluster &nbsp;&nbsp;&nbsp;&nbsp;connect_timeout: 0.25s &nbsp;&nbsp;&nbsp;&nbsp;type: STATIC &nbsp;&nbsp;&nbsp;&nbsp;lb_policy: ROUND_ROBIN &nbsp;&nbsp;&nbsp;&nbsp;http2_protocol_options: {} &nbsp;&nbsp;&nbsp;&nbsp;upstream_connection_options: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# configure a TCP keep-alive to detect and reconnect to the admin &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;# server in the event of a TCP socket half open connection &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;tcp_keepalive: {} &nbsp;&nbsp;&nbsp;&nbsp;load_assignment: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cluster_name: xds_cluster &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;endpoints: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- lb_endpoints: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- endpoint: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;socket_address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: 127.0.0.1 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;port_value: 5678 </td> 
 </tr> 
 </tbody> 
</table>

上例为gRPC/HTTP2方式动态拉取配置，提供配置的服务名为xds\_cluster，服务端口为“127.0.0.1:5678”。

1.  1.  1.   **gRPC接口**
2.  CDS

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> POST /envoy.api.v2.ClusterDiscoveryService/StreamClusters </td> 
 </tr> 
 </tbody> 
</table>

gRPC服务定义在文件[cds.proto][]，链接地址：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> <a href="https://github.com/envoyproxy/envoy/blob/v1.12.2/api/envoy/api/v2/cds.proto" rel="nofollow">https://github.com/envoyproxy/envoy/blob/v1.12.2/api/envoy/api/v2/cds.proto</a> </td> 
 </tr> 
 </tbody> 
</table>

1.  EDS

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> POST /envoy.api.v2.EndpointDiscoveryService/StreamEndpoints </td> 
 </tr> 
 </tbody> 
</table>

gRPC服务定义在文件[eds.proto][]，链接地址：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> <a href="https://github.com/envoyproxy/envoy/blob/v1.12.2/api/envoy/api/v2/eds.proto" rel="nofollow">https://github.com/envoyproxy/envoy/blob/v1.12.2/api/envoy/api/v2/eds.proto</a> </td> 
 </tr> 
 </tbody> 
</table>

1.  LDS

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> POST /envoy.api.v2.ListenerDiscoveryService/StreamListeners </td> 
 </tr> 
 </tbody> 
</table>

gRPC服务定义在文件[lds.proto][]，链接地址：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> <a href="https://github.com/envoyproxy/envoy/blob/v1.12.2/api/envoy/api/v2/lds.proto" rel="nofollow">https://github.com/envoyproxy/envoy/blob/v1.12.2/api/envoy/api/v2/lds.proto</a> </td> 
 </tr> 
 </tbody> 
</table>

1.  RDS

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> POST /envoy.api.v2.RouteDiscoveryService/StreamRoutes </td> 
 </tr> 
 </tbody> 
</table>

gRPC服务定义在文件[rds.proto][]，链接地址：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> <a href="https://github.com/envoyproxy/envoy/blob/v1.12.2/api/envoy/api/v2/rds.proto" rel="nofollow">https://github.com/envoyproxy/envoy/blob/v1.12.2/api/envoy/api/v2/rds.proto</a> </td> 
 </tr> 
 </tbody> 
</table>

1.  1.  1.   **REST接口**
2.  CDS

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> POST /v2/discovery:clusters </td> 
 </tr> 
 </tbody> 
</table>

1.  EDS

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> POST /v2/discovery:endpoints </td> 
 </tr> 
 </tbody> 
</table>

1.  LDS

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> POST /v2/discovery:listeners </td> 
 </tr> 
 </tbody> 
</table>

1.  RDS

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> POST /v2/discovery:routes </td> 
 </tr> 
 </tbody> 
</table>

1.   **试跑体验**

试跑Enovy要求有[Docker][]基础（如无基础可参考《[Docker入门之安装Docker][Docker]》和《[Docker入门之创建镜像初步][Docker 1]》），从源代码构建会有些复杂，所以本文直接使用官方提供的Docker景象作为试跑对象。试跑前提要求Docker环境已准备好，并且试跑机要能访问外网。

1.  1.   **体验目标**

代理**https**://www.baidu.com，当访问本机的8080端口时，实际为访问被代理的**https**://www.baidu.com。

1.  1.   **下载Envoy镜像**

执行下列命令拉取Envoy的Docker镜像：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> docker pull&nbsp;envoyproxy/envoy </td> 
 </tr> 
 </tbody> 
</table>

1.  1.   **准备Envoy配置文件**

在本地主备配置文件“/tmp/bd.yaml”，文件内容如下：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> $ cat /tmp/bd.yaml admin: &nbsp;&nbsp;access_log_path: /tmp/admin_access.log &nbsp;&nbsp;address: &nbsp;&nbsp;&nbsp;&nbsp;socket_address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;protocol: TCP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: 0.0.0.0&nbsp;# 管理地址 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;port_value: 8081&nbsp;# 管理端口 &nbsp; static_resources: &nbsp;&nbsp;listeners: # 监听器数组 &nbsp;&nbsp;- name: listener_0 # 监听器 &nbsp;&nbsp;&nbsp;&nbsp;address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;socket_address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;protocol: TCP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: 0.0.0.0 # 监听地址 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;port_value: 8080&nbsp;# 监听端口 &nbsp;&nbsp;&nbsp;&nbsp;filter_chains:&nbsp;# 过滤器链 &nbsp;&nbsp;&nbsp;&nbsp;- filters:&nbsp;# 过滤器数组 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- name: envoy.http_connection_manager&nbsp;# 过滤器名 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;typed_config: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"@type":&nbsp;type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;stat_prefix: ingress_http &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;route_config:&nbsp;# 路由配置 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;name: local_route&nbsp;# 路由配置名 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;virtual_hosts:&nbsp;# 虚拟主机数组 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- name: local_service &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;domains: ["*"]&nbsp;# 需代理的域名数组 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;routes:&nbsp;# 定义路由 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- match: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;prefix: "/"&nbsp;# 匹配规则 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;route: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;host_rewrite: www.baidu.com&nbsp;# 将HOST重写为 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cluster: bd_service&nbsp;# 下游集群名，通过它找到下游集群的配置 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http_filters: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- name: envoy.router &nbsp;&nbsp;clusters:&nbsp;# 下游集群数组 &nbsp;&nbsp;- name: bd_service&nbsp;# 下游集群名 &nbsp;&nbsp;&nbsp;&nbsp;connect_timeout: 0.25s&nbsp;# 连接下游的超时时长 &nbsp;&nbsp;&nbsp;&nbsp;type: LOGICAL_DNS &nbsp;&nbsp;&nbsp;&nbsp;# Comment out the following line to test on v6 networks &nbsp;&nbsp;&nbsp;&nbsp;dns_lookup_family: V4_ONLY&nbsp;# 域名查找范围，这里表示只查找IPV4地址 &nbsp;&nbsp;&nbsp;&nbsp;lb_policy: ROUND_ROBIN&nbsp;# 负载均衡策略 &nbsp;&nbsp;&nbsp;&nbsp;load_assignment: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cluster_name: bd_service &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;endpoints: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- lb_endpoints: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- endpoint: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;socket_address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: www.baidu.com &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;port_value: 443 &nbsp;&nbsp;&nbsp;&nbsp;transport_socket: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;name: envoy.transport_sockets.tls &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;typed_config: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"@type": type.googleapis.com/envoy.api.v2.auth.UpstreamTlsContext &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;sni: <a href="http://www.baidu.com" rel="nofollow">www.baidu.com</a> &nbsp; </td> 
 </tr> 
 </tbody> 
</table>

由于代理的是域名www.baidu.com，所以**clusters**的**type**值需为**LOGICAL\_DNS**或strict\_dns，type还有如下几个取值（不区分大小写）：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:66.35pt;"> STATIC </td> 
 <td style="vertical-align:top;width:359.75pt;"> 缺省值，在集群中列出所有可代理的主机（Endpoints） </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:66.35pt;"> LOGICAL_DNS </td> 
 <td style="vertical-align:top;width:359.75pt;"> Envoy使用DNS添加主机，但如果DNS不再返回时，也不会丢弃 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:66.35pt;"> STRICT_DNS </td> 
 <td style="vertical-align:top;width:359.75pt;"> Envoy将监控DNS，而每个匹配的A记录都将被认为是有效的 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:66.35pt;"> OriginalDst </td> 
 <td style="vertical-align:top;width:359.75pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:66.35pt;"> EDS </td> 
 <td style="vertical-align:top;width:359.75pt;"> Envoy调用一个外部的gRPC或REST服务查找被代理的主机（Endpoints） </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:66.35pt;"> 自定义值 </td> 
 <td style="vertical-align:top;width:359.75pt;"> &nbsp; </td> 
 </tr> 
 </tbody> 
</table>

访问https://www.baidu.com，一定要配置**transport\_socket**，否则将报错“upstream connect error or disconnect/reset before headers. reset reason: connection failure”。如果是访问http://www.baidu.com，则不用配置transport\_socket，**sni**不是必须的。

1.  1.   **启动Envoy容器**

在宿主机上，执行下列命令启动Envoy容器：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> docker run -it --rm -v=/tmp:/tmp -p&nbsp;8080:8080 -p&nbsp;8081:8081 envoyproxy/envoy&nbsp;bash </td> 
 </tr> 
 </tbody> 
</table>

可在宿主机上执行命令“docker ps|grep envoy”，检查Envoy容器是否起来了。

1.  1.   **启动Envoy进程**

在Envoy容器中，执行下列命令拉起Envoy进程：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> envoy&nbsp;-c&nbsp;/tmp/bd.yaml </td> 
 </tr> 
 </tbody> 
</table>

启动成功可看到如下日志：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> [info][config] [source/server/configuration_impl.cc:62] loading 0 static secret(s) [info][config] [source/server/configuration_impl.cc:68] loading 1 cluster(s) [info][config] [source/server/configuration_impl.cc:72] loading 1 listener(s) [info][config] [source/server/configuration_impl.cc:97] loading tracing configuration [info][config] [source/server/configuration_impl.cc:117] loading stats sink configuration [info][main] [source/server/server.cc:549] starting main dispatch loop [info][upstream] [source/common/upstream/cluster_manager_impl.cc:161] cm init: all clusters initialized [info][main] [source/server/server.cc:528] all clusters initialized. initializing init manager [info][config] [source/server/listener_manager_impl.cc:578] all dependencies initialized. starting workers </td> 
 </tr> 
 </tbody> 
</table>

1.  1.   **体验效果**

假设Envoy容器所在机器IP为192.168.1.21，则访问http://192.168.1.21:8080等同于访问https://www.baidu.com。

1.   **动态配置**
    
    1.   **动态配置EDS**

Envoy定时访问EDS服务取EDS配置。

1.  1.  1.   **Envoy配置文件**

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> $ cat /tmp/bd.yaml admin: &nbsp;&nbsp;access_log_path: /tmp/admin_access.log &nbsp;&nbsp;address: &nbsp;&nbsp;&nbsp;&nbsp;socket_address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;protocol: TCP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: 0.0.0.0 # 管理地址 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;port_value: 8081 # 管理端口 &nbsp; static_resources: &nbsp;&nbsp;listeners: # 监听器数组 &nbsp;&nbsp;- name: listener_0 # 监听器 &nbsp;&nbsp;&nbsp;&nbsp;address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;socket_address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;protocol: TCP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: 0.0.0.0 # 监听地址 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;port_value: 8080 # 监听端口 &nbsp;&nbsp;&nbsp;&nbsp;filter_chains: # 过滤器链 &nbsp;&nbsp;&nbsp;&nbsp;- filters: # 过滤器数组 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- name: envoy.http_connection_manager # 过滤器名 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;typed_config: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"@type": type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;stat_prefix: ingress_http &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;route_config: # 路由配置 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;name: local_route # 路由配置名 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;virtual_hosts: # 虚拟主机数组 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- name: local_service &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;domains: ["*"] # 需代理的域名数组 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;routes: # 定义路由 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- match: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;prefix: "/" # 匹配规则 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;route: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;host_rewrite: www.baidu.com # 将HOST重写为 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cluster: bd_service&nbsp;# 下游集群名，通过它找到下游集群的配置 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http_filters: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- name: envoy.router &nbsp;&nbsp;clusters: # 下游集群数组 &nbsp;&nbsp;- name: bd_service&nbsp;# 下游集群名 &nbsp;&nbsp;&nbsp;&nbsp;connect_timeout: 0.25s # 连接下游的超时时长 &nbsp;&nbsp;&nbsp;&nbsp;type: eds &nbsp;&nbsp;&nbsp;&nbsp;lb_policy: ROUND_ROBIN # 负载均衡策略 &nbsp;&nbsp;&nbsp;&nbsp;eds_cluster_config: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;eds_config: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;api_config_source: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;api_type: rest &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;refresh_delay: "10s" # 动态一定要有这个配置 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cluster_names: [xds_cluster] # 这里并不提供静态的endpoints，需访问EDS服务得到 &nbsp;&nbsp;&nbsp;&nbsp;transport_socket: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;name: envoy.transport_sockets.tls &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;typed_config: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"@type": type.googleapis.com/envoy.api.v2.auth.UpstreamTlsContext &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;sni: www.baidu.com &nbsp;&nbsp;- name: xds_cluster &nbsp;&nbsp;&nbsp;&nbsp;connect_timeout: 0.25s &nbsp;&nbsp;&nbsp;&nbsp;type: static &nbsp;&nbsp;&nbsp;&nbsp;lb_policy: ROUND_ROBIN &nbsp;&nbsp;&nbsp;&nbsp;load_assignment: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cluster_name: xds_cluster &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;endpoints: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- lb_endpoints: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- endpoint: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;socket_address: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;address: 127.0.0.1 # EDS的服务地址 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;port_value: 2020 # EDS的服务端口 </td> 
 </tr> 
 </tbody> 
</table>

1.  1.  1.   **EDS服务源码**

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> // 演示Envoy的动态EDS（Endpoint Discovery Service） // 执行命令“go build eds.go ”，即生成可执行程序eds package main &nbsp; import&nbsp;( &nbsp;&nbsp;"encoding/json" &nbsp;&nbsp;"fmt" &nbsp;&nbsp;"net/http" &nbsp;&nbsp;"time" ) &nbsp; // { // &nbsp;&nbsp;"version_info": "0", // &nbsp;&nbsp;"resources": [ // &nbsp;&nbsp;&nbsp;&nbsp;{ // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"@type": "type.googleapis.com/envoy.api.v2.ClusterLoadAssignment", // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"cluster_name": "some_service", // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"endpoints": [ // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{ // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"lb_endpoints": [ // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{ // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"endpoint": { // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"address": { // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"socket_address": { // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"address": "127.0.0.2", // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"port_value": 1234 // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;} // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;} // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;} // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;} // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;] // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;} // &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;] // &nbsp;&nbsp;&nbsp;&nbsp;} // &nbsp;&nbsp;] // } &nbsp; type SocketAddress struct { &nbsp;&nbsp;Address string `json:"address"` &nbsp;&nbsp;PortValue int `json:"port_value"` } &nbsp; type Address struct { &nbsp;&nbsp;SocketAddress SocketAddress `json:"socket_address"` } &nbsp; type Endpoint struct { &nbsp;&nbsp;Address Address `json:"address"` } &nbsp; type LbEndpoint struct { &nbsp;&nbsp;Endpoint Endpoint `json:"endpoint"` } &nbsp; type LbEndpoints struct { &nbsp;&nbsp;LbEndpoints []LbEndpoint `json:"lb_endpoints"` } &nbsp; type Resource struct { &nbsp;&nbsp;Type string `json:"@type"` &nbsp;&nbsp;ClusterName string `json:"cluster_name"` &nbsp;&nbsp;Endpoints []LbEndpoints `json:"endpoints"` } &nbsp; type EDS struct { &nbsp;&nbsp;VersionInfo string `json:"version_info"` &nbsp;&nbsp;Resources []Resource `json:"resources"` } &nbsp; func DiscoveryEndpointsHandler(w http.ResponseWriter, r *http.Request) { &nbsp;&nbsp;// LbEndpoint &nbsp;&nbsp;var lb_endpoint1 LbEndpoint &nbsp;&nbsp;lb_endpoint1.Endpoint.Address.SocketAddress.Address = "180.101.49.12" &nbsp;&nbsp;lb_endpoint1.Endpoint.Address.SocketAddress.PortValue = 443 &nbsp; &nbsp;&nbsp;// LbEndpoint &nbsp;&nbsp;var lb_endpoint2 LbEndpoint &nbsp;&nbsp;lb_endpoint2.Endpoint.Address.SocketAddress.Address = "180.101.49.11" &nbsp;&nbsp;lb_endpoint2.Endpoint.Address.SocketAddress.PortValue = 443 &nbsp; &nbsp;&nbsp;// LbEndpoint &nbsp;&nbsp;var lb_endpoint3 LbEndpoint &nbsp;&nbsp;lb_endpoint3.Endpoint.Address.SocketAddress.Address = "14.215.177.38" &nbsp;&nbsp;lb_endpoint3.Endpoint.Address.SocketAddress.PortValue = 443 &nbsp; &nbsp;&nbsp;// LbEndpoints &nbsp;&nbsp;var lb_endpoints LbEndpoints &nbsp;&nbsp;lb_endpoints.LbEndpoints = append(lb_endpoints.LbEndpoints, lb_endpoint1) &nbsp;&nbsp;lb_endpoints.LbEndpoints = append(lb_endpoints.LbEndpoints, lb_endpoint2) &nbsp;&nbsp;lb_endpoints.LbEndpoints = append(lb_endpoints.LbEndpoints, lb_endpoint3) &nbsp; &nbsp;&nbsp;// Resource &nbsp;&nbsp;var resource Resource &nbsp;&nbsp;resource.Type = "type.googleapis.com/envoy.api.v2.ClusterLoadAssignment" &nbsp;&nbsp;resource.ClusterName = "bd_service" &nbsp;&nbsp;resource.Endpoints = append(resource.Endpoints, lb_endpoints) &nbsp; &nbsp;&nbsp;// EDS &nbsp;&nbsp;var eds EDS &nbsp;&nbsp;eds.VersionInfo = "0" &nbsp;&nbsp;eds.Resources = append(eds.Resources, resource) &nbsp; &nbsp;&nbsp;// struct to json &nbsp;&nbsp;jsonBytes, err := json.Marshal(eds) &nbsp;&nbsp;if err != nil { &nbsp;&nbsp;&nbsp;&nbsp;fmt.Println(err) &nbsp;&nbsp;} &nbsp; &nbsp;&nbsp;// json to string &nbsp;&nbsp;str := string(jsonBytes) &nbsp; &nbsp;&nbsp;// output json string &nbsp;&nbsp;now := time.Now() &nbsp;&nbsp;// 注意只能是“2006-01-02 15:04:05” &nbsp;&nbsp;fmt.Printf("[%s] %s\n", now.Format("2006-01-02 15:04:05"), string(jsonBytes)) &nbsp;&nbsp;fmt.Println(str) &nbsp;&nbsp;fmt.Fprintln(w, str) } &nbsp; func main() { &nbsp;&nbsp;http.HandleFunc("/v2/discovery:endpoints", DiscoveryEndpointsHandler) &nbsp;&nbsp;http.ListenAndServe("0.0.0.0:2020", nil) } </td> 
 </tr> 
 </tbody> 
</table>

1.  1.  1.   **启动EDS进程**

先将程序xds复制到容器中（以容器ID为**0779d56f4f65**为例）：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> docker cp&nbsp;eds 0779d56f4f65:/tmp </td> 
 </tr> 
 </tbody> 
</table>

进入容器：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> docker container exec&nbsp;-it 0779d56f4f65&nbsp;/bin/bash </td> 
 </tr> 
 </tbody> 
</table>

然后，在Envoy容器中启动EDS进程：

1.  1.  1.   **启动Envoy进程**

在Envoy容器中启动Envoy进程：

<table style="width:426.1pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:426.1pt;"> envoy -c /tmp/bd.yaml&nbsp;--service-cluster xds_cluster --service-node 1 </td> 
 </tr> 
 </tbody> 
</table>

[Envoy-1.12.2]: https://www.envoyproxy.io/docs/envoy/v1.12.2/configuration/overview/v2_overview
[Envoy]: https://www.envoyproxy.io/
[Istio]: https://istio.io/
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy_size_16_color_FFFFFF_t_70]: https://img-blog.csdnimg.cn/20200107103332492.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy,size_16,color_FFFFFF,t_70
[https_github.com_envoyproxy_envoy]: https://github.com/envoyproxy/envoy
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy_size_16_color_FFFFFF_t_70 1]: https://img-blog.csdnimg.cn/20200107103342138.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy,size_16,color_FFFFFF,t_70
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy_size_16_color_FFFFFF_t_70 2]: https://img-blog.csdnimg.cn/20200107103407979.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy,size_16,color_FFFFFF,t_70
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy_size_16_color_FFFFFF_t_70 3]: https://img-blog.csdnimg.cn/20200107103422477.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy,size_16,color_FFFFFF,t_70
[20200107103432814.jpg]: https://img-blog.csdnimg.cn/20200107103432814.jpg
[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy_size_16_color_FFFFFF_t_70 4]: https://img-blog.csdnimg.cn/20200107103509796.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L0FxdWVzdGVy,size_16,color_FFFFFF,t_70
[cds.proto]: https://github.com/envoyproxy/envoy/blob/v1.12.2/api/envoy/api/v2/cds.proto
[eds.proto]: https://github.com/envoyproxy/envoy/blob/v1.12.2/api/envoy/api/v2/eds.proto
[lds.proto]: https://github.com/envoyproxy/envoy/blob/v1.12.2/api/envoy/api/v2/lds.proto
[rds.proto]: https://github.com/envoyproxy/envoy/blob/v1.12.2/api/envoy/api/v2/rds.proto
[Docker]: https://blog.csdn.net/Aquester/article/details/103620684
[Docker 1]: https://blog.csdn.net/Aquester/article/details/103671589