Overview (v2 API)

    • Streaming delivery of API updates via gRPC. This reduces resource requirements and can lower the update latency.
    • A new REST-JSON API in which the JSON/YAML formats are derived mechanically via the proto3 canonical JSON mapping.
    • Delivery of updates via the filesystem, REST-JSON or gRPC endpoints.
    • Advanced load balancing through an extended endpoint assignment API and load and resource utilization reporting to management servers.
    • when needed. The v2 APIs still maintain a baseline eventual consistency model.

    See the xDS protocol description for further details on aspects of v2 message exchange between Envoy and the management server.

    To use the v2 API, it’s necessary to supply a bootstrap configuration file. This provides static server configuration and configures Envoy to access . As with the v1 JSON/YAML configuration, this is supplied on the command-line via the flag, i.e.:

    where the extension reflects the underlying v2 config representation. The flag is not strictly required as Envoy will attempt to autodetect the config file version, but this option provides an enhanced debug experience when configuration parsing fails.

    The Bootstrap message is the root of the configuration. A key concept in the message is the distinction between static and dynamic resouces. Resources such as a Listener or may be supplied either statically in static_resources or have an xDS service such as or CDS configured in .

    Example

    Below we will use YAML representation of the config protos and a running example of a service proxying HTTP from 127.0.0.1:10000 to 127.0.0.2:1234.

    A minimal fully static bootstrap config is provided below:

    1. admin:
    2.   access_log_path: /tmp/admin_access.log
    3.   address:
    4.     socket_address: { address: 127.0.0.1, port_value: 9901 }
    6. static_resources:
    7.   listeners:
    8.   - name: listener_0
    9.     address:
    10.       socket_address: { address: 127.0.0.1, port_value: 10000 }
    11.     filter_chains:
    12.     - filters:
    13.       - name: envoy.http_connection_manager
    14.         config:
    15.           stat_prefix: ingress_http
    16.           codec_type: AUTO
    17.           route_config:
    18.             name: local_route
    19.             virtual_hosts:
    20.             - name: local_service
    21.               domains: ["*"]
    22.               routes:
    23.               - match: { prefix: "/" }
    24.                 route: { cluster: some_service }
    25.           http_filters:
    26.           - name: envoy.router
    27.   clusters:
    28.   - name: some_service
    29.     connect_timeout: 0.25s
    30.     type: STATIC
    31.     lb_policy: ROUND_ROBIN
    32.     hosts: [{ socket_address: { address: 127.0.0.2, port_value: 1234 }}]

    A bootstrap config that continues from the above example with dynamic endpoint discovery via an gRPC management server listening on 127.0.0.3:5678 is provided below:

    1. admin:
    2.   access_log_path: /tmp/admin_access.log
    3.   address:
    4.     socket_address: { address: 127.0.0.1, port_value: 9901 }
    6. static_resources:
    7.   listeners:
    8.   - name: listener_0
    9.     address:
    10.       socket_address: { address: 127.0.0.1, port_value: 10000 }
    11.     filter_chains:
    12.     - filters:
    13.       - name: envoy.http_connection_manager
    14.         config:
    15.           stat_prefix: ingress_http
    16.           codec_type: AUTO
    17.           route_config:
    18.             name: local_route
    19.             - name: local_service
    20.               domains: ["*"]
    21.               routes:
    22.               - match: { prefix: "/" }
    23.                 route: { cluster: some_service }
    24.           http_filters:
    25.           - name: envoy.router
    26.   clusters:
    27.   - name: some_service
    28.     connect_timeout: 0.25s
    29.     lb_policy: ROUND_ROBIN
    30.     type: EDS
    31.     eds_cluster_config:
    32.       eds_config:
    33.         api_config_source:
    35.           cluster_names: [xds_cluster]
    36.   - name: xds_cluster
    37.     connect_timeout: 0.25s
    38.     type: STATIC
    39.     lb_policy: ROUND_ROBIN
    40.     http2_protocol_options: {}
    41.     hosts: [{ socket_address: { address: 127.0.0.3, port_value: 5678 }}]

    Notice above that xds_cluster is defined to point Envoy at the management server. Even in an otherwise completely dynamic configurations, some static resources need to be defined to point Envoy at its xDS management server(s).

    In the above example, the EDS management server could then return a proto encoding of a DiscoveryResponse:

    1. version_info: "0"
    2. resources:
    3. - "@type": type.googleapis.com/envoy.api.v2.ClusterLoadAssignment
    4.   cluster_name: some_service
    5.   endpoints:
    6.   - lb_endpoints:
    7.     - endpoint:
    8.         address:
    9.           socket_address:
    10.             address: 127.0.0.2
    11.             port_value: 1234

    The versioning and type URL scheme that appear above are explained in more detail in the documentation.

    A fully dynamic bootstrap configuration, in which all resources other than those belonging to the management server are discovered via xDS is provided below:

    1. admin:
    2.   access_log_path: /tmp/admin_access.log
    3.   address:
    4.     socket_address: { address: 127.0.0.1, port_value: 9901 }
    6. dynamic_resources:
    7.   lds_config:
    8.     api_config_source:
    9.       api_type: GRPC
    10.       cluster_names: [xds_cluster]
    11.   cds_config:
    12.     api_config_source:
    13.       api_type: GRPC
    14.       cluster_names: [xds_cluster]
    16. static_resources:
    17.   clusters:
    18.   - name: xds_cluster
    19.     connect_timeout: 0.25s
    20.     type: STATIC
    21.     lb_policy: ROUND_ROBIN
    22.     http2_protocol_options: {}
    23.     hosts: [{ socket_address: { address: 127.0.0.3, port_value: 5678 }}]

    The management server could respond to LDS requests with:

    1. version_info: "0"
    2. resources:
    3. - "@type": type.googleapis.com/envoy.api.v2.Listener
    4.   name: listener_0
    5.   address:
    6.     socket_address:
    7.       address: 127.0.0.1
    8.       port_value: 10000
    9.   filter_chains:
    10.     - name: envoy.http_connection_manager
    11.       config:
    12.         stat_prefix: ingress_http
    13.         codec_type: AUTO
    14.         rds:
    15.           route_config_name: local_route
    16.           config_source:
    17.             api_config_source:
    18.               api_type: GRPC
    19.               cluster_names: [xds_cluster]
    20.         http_filters:
    21.         - name: envoy.router

    The management server could respond to RDS requests with:

    The management server could respond to CDS requests with:

    1. version_info: "0"
    2. resources:
    3. - "@type": type.googleapis.com/envoy.api.v2.Cluster
    4.   name: some_service
    6.   lb_policy: ROUND_ROBIN
    7.   type: EDS
    8.   eds_cluster_config:
    9.     eds_config:
    10.       api_config_source:
    11.         api_type: GRPC
    12.         cluster_names: [xds_cluster]

    The management server could respond to EDS requests with:

    1. version_info: "0"
    2. resources:
    3. - "@type": type.googleapis.com/envoy.api.v2.ClusterLoadAssignment
    4.   cluster_name: some_service
    5.   endpoints:
    6.   - lb_endpoints:
    7.     - endpoint:
    8.         address:
    9.           socket_address:
    10.             address: 127.0.0.2
    11.             port_value: 1234

    A v2 xDS management server will implement the below endpoints as required for gRPC and/or REST serving. In both streaming gRPC and REST-JSON cases, a DiscoveryRequest is sent and a received following the xDS protocol.

    POST /envoy.api.v2.ClusterDiscoveryService/StreamClusters

    See cds.proto for the service definition. This is used by Envoy as a client when

    1. cds_config:
    2.   api_config_source:
    3.     api_type: GRPC
    4.     cluster_names: [some_xds_cluster]

    POST /envoy.api.v2.EndpointDiscoveryService/StreamEndpoints

    See eds.proto for the service definition. This is used by Envoy as a client when

    1. eds_config:
    2.   api_config_source:
    3.     api_type: GRPC
    4.     cluster_names: [some_xds_cluster]

    is set in the field of the Cluster config.

    POST /envoy.api.v2.ListenerDiscoveryService/StreamListeners

    See lds.proto for the service definition. This is used by Envoy as a client when

    1. lds_config:
    2.   api_config_source:
    3.     api_type: GRPC
    4.     cluster_names: [some_xds_cluster]

    is set in the of the Bootstrap config.

    POST /envoy.api.v2.RouteDiscoveryService/StreamRoutes

    See rds.proto for the service definition. This is used by Envoy as a client when

    is set in the field of the HttpConnectionManager config.

    POST /v2/discovery:clusters

    See cds.proto for the service definition. This is used by Envoy as a client when

    1. cds_config:
    2.   api_config_source:
    3.     api_type: REST
    4.     cluster_names: [some_xds_cluster]

    is set in the of the Bootstrap config.

    POST /v2/discovery:endpoints

    See eds.proto for the service definition. This is used by Envoy as a client when

    1. eds_config:
    2.   api_config_source:
    3.     api_type: REST
    4.     cluster_names: [some_xds_cluster]

    is set in the field of the Cluster config.

    POST /v2/discovery:listeners

    See lds.proto for the service definition. This is used by Envoy as a client when

    1. lds_config:
    2.   api_config_source:
    3.     api_type: REST
    4.     cluster_names: [some_xds_cluster]

    is set in the of the Bootstrap config.

    See for the service definition. This is used by Envoy as a client when

    1. route_config_name: some_route_name
    2. config_source:
    3.   api_config_source:
    4.     api_type: REST
    5.     cluster_names: [some_xds_cluster]

    is set in the rds field of the config.

    Aggregated Discovery Service

    While Envoy fundamentally employs an eventual consistency model, ADS provides an opportunity to sequence API update pushes and ensure affinity of a single management server for an Envoy node for API updates. ADS allows one or more APIs and their resources to be delivered on a single, bidirectional gRPC stream by the management server. Without this, some APIs such as RDS and EDS may require the management of multiple streams and connections to distinct management servers.

    ADS will allow for hitless updates of configuration by appropriate sequencing. For example, suppose foo.com was mappped to cluster X. We wish to change the mapping in the route table to point foo.com at cluster Y. In order to do this, a CDS/EDS update must first be delivered containing both clusters X and Y.

    Without ADS, the CDS/EDS/RDS streams may point at distinct management servers, or when on the same management server at distinct gRPC streams/connections that require coordination. The EDS resource requests may be split across two distinct streams, one for X and one for Y. ADS allows these to be coalesced to a single stream to a single management server, avoiding the need for distributed synchronization to correctly sequence the update. With ADS, the management server would deliver the CDS, EDS and then RDS updates on a single stream.

    ADS is only available for gRPC streaming (not REST) and is described more fully in this document. The gRPC endpoint is:

    POST /envoy.api.v2.AggregatedDiscoveryService/StreamAggregatedResources

    See discovery.proto for the service definition. This is used by Envoy as a client when

    1. ads_config:
    2.   api_type: GRPC

    is set in the of the Bootstrap config.

    When this is set, any of the configuration sources can be set to use the ADS channel. For example, a LDS config could be changed from

    to

    1. lds_config: {ads: {}}

    with the effect that the LDS stream will be directed to some_ads_cluster over the shared ADS channel.

    When Envoy instance looses connectivity with the management server, Envoy will latch on to the previous configuration while actively retrying in the background to reestablish the connection with the management server.

    Envoy debug logs the fact that it is not able to establish a connection with the management server every time it attempts a connection.

    upstream_cx_connect_fail a cluster level statistic of the cluster pointing to management server provides a signal for monitoring this behavior.

    Status

    All features described in the are implemented unless otherwise noted. In the v2 API reference and the v2 API repository, all protos are frozen unless they are tagged as draft or experimental. Here, frozen means that we will not break wire format compatibility.

    Frozen protos may be further extended, e.g. by adding new fields, in a manner that does not break . Fields in the above protos may be later deprecated, subject to the breaking change policy, when their related functionality is no longer required. While frozen APIs have their wire format compatibility preserved, we reserve the right to change proto namespaces, file locations and nesting relationships, which may cause breaking code changes. We will aim to minimize the churn here.

    Protos tagged draft, meaning that they are near finalized, are likely to be at least partially implemented in Envoy but may have wire format breaking changes made prior to freezing.

    The current open v2 API issues are tracked .