Common types

    Identifies location of where either Envoy runs or where upstream hosts run.

    region

    () Region this zone belongs to.

    zone

    () Defines the local service zone where Envoy is running. Though optional, it should be set if discovery service routing is used and the discovery service exposes zone data, either in this message or via . The meaning of zone is context dependent, e.g. Availability Zone (AZ) on AWS, on GCP, etc.

    sub_zone

    (string) When used for locality of upstream hosts, this field further splits zone into smaller chunks of sub-zones so they can be load balanced independently.

    core.Node

    Identifies a specific Envoy instance. The node identifier is presented to the management server, which may use this identifier to distinguish per Envoy configuration for serving.

    1. {
    2.   "id": "...",
    3.   "cluster": "...",
    4.   "metadata": "{...}",
    5.   "locality": "{...}",
    6.   "build_version": "..."

    id

    (string) An opaque node identifier for the Envoy node. This also provides the local service node name. It should be set if any of the following features are used: , CDS, and , either in this message or via --service-node.

    cluster

    () Defines the local service cluster name where Envoy is running. Though optional, it should be set if any of the following features are used: statsd, , runtime override directory, , HTTP global rate limiting, , and HTTP tracing, either in this message or via .

    metadata

    (Struct) Opaque metadata extending the node identifier. Envoy will pass this directly to the management server.

    locality

    () Locality specifying where the Envoy instance is running.

    build_version

    (string) This is motivated by informing a management server during canary which version of Envoy is being tested in a heterogeneous fleet. This will be set by Envoy in management server RPCs.

    core.Metadata

    Metadata provides additional inputs to filters based on matched listeners, filter chains, routes and endpoints. It is structured as a map from filter name (in reverse DNS format) to metadata specific to the filter. Metadata key-values for a filter are merged as connection and request handling occurs, with later values for the same key overriding earlier values.

    An example use of metadata is providing additional values to http_connection_manager in the envoy.http_connection_manager.access_log namespace.

    For load balancing, Metadata provides a means to subset cluster endpoints. Endpoints have a Metadata object associated and routes contain a Metadata object to match against. There are some well defined metadata used today for this purpose:

    • {"envoy.lb": {"canary": <bool> }} This indicates the canary status of an endpoint and is also used during header processing (x-envoy-upstream-canary) and for stats purposes.

    filter_metadata

    (map<string, >) Key is the reverse DNS filter name, e.g. com.acme.widget. The envoy.* namespace is reserved for Envoy’s built-in filters.

    [core.RuntimeUInt32 proto]

    Runtime derived uint32 with a default when not specified.

    1. {
    2.   "runtime_key": "..."

    default_value

    runtime_key

    (, REQUIRED) Runtime key to get value for comparison. This value is used if defined.

    core.HeaderValue

    [core.HeaderValue proto]

    Header name/value pair.

    key

    () Header name.

    value

    (string) Header value.

    The same as used for HTTP access logging applies here, however unknown header values are replaced with the empty string instead of -.

    core.HeaderValueOption

    Header name/value pair plus option to control append behavior.

    1. {
    2.   "header": "{...}",
    3.   "append": "{...}"
    4. }

    header

    (core.HeaderValue) Header name/value pair that this option applies to.

    append

    () Should the value be appended? If true (default), the value is appended to existing values.

    [core.DataSource proto]

    Data source consisting of either a file or an inline value.

    filename

    (, REQUIRED) Local filesystem data source.

    Precisely one of filename, , inline_string must be set.

    inline_bytes

    () Bytes inlined in the configuration.

    Precisely one of filename, , inline_string must be set.

    inline_string

    (, REQUIRED) String inlined in the configuration.

    Precisely one of filename, , inline_string must be set.

    core.TransportSocket

    Configuration for transport socket in listeners and . If the configuration is empty, a default transport socket implementation and configuration will be chosen based on the platform and existence of tls_context.

    1. {
    2.   "name": "...",

    (string, REQUIRED) The name of the transport socket to instantiate. The name must match a supported transport socket implementation.

    config

    () Implementation specific configuration which depends on the implementation being instantiated. See the supported transport socket implementations for further documentation.

    Enum core.RoutingPriority

    [core.RoutingPriority proto]

    Envoy supports both at the route and the virtual cluster level. The current priority implementation uses different connection pool and circuit breaking settings for each priority level. This means that even for HTTP/2 requests, two physical connections will be used to an upstream host. In the future Envoy will likely support true HTTP/2 priority over a single upstream connection.

    DEFAULT

    (DEFAULT) ⁣

    HIGH

    ⁣

    [core.RequestMethod proto]

    HTTP request method.

    METHOD_UNSPECIFIED

    (DEFAULT) ⁣

    GET

    ⁣

    HEAD

    ⁣

    POST

    ⁣

    PUT

    ⁣

    DELETE

    ⁣

    CONNECT

    ⁣

    OPTIONS

    ⁣

    TRACE