|
|
|
@ -9,35 +9,47 @@ import "google/protobuf/duration.proto"; |
|
|
|
|
import "google/protobuf/struct.proto"; |
|
|
|
|
import "google/protobuf/wrappers.proto"; |
|
|
|
|
|
|
|
|
|
// [#protodoc-title: Common configuration elements] |
|
|
|
|
import "validate/validate.proto"; |
|
|
|
|
|
|
|
|
|
// [#protodoc-title: Common types] |
|
|
|
|
|
|
|
|
|
// Identifies location of where either Envoy runs or where upstream hosts run. |
|
|
|
|
message Locality { |
|
|
|
|
// Region this zone belongs to. |
|
|
|
|
// Region this :ref:`zone <envoy_api_field_Locality.zone>` belongs to. |
|
|
|
|
string region = 1; |
|
|
|
|
|
|
|
|
|
// Availability Zone (AZ) in AWS, Zone in GCP. |
|
|
|
|
// `Availability Zone (AZ) |
|
|
|
|
// <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html>`_ |
|
|
|
|
// on AWS, `Zone <https://cloud.google.com/compute/docs/regions-zones/>`_ on |
|
|
|
|
// GCP, etc. |
|
|
|
|
string zone = 2; |
|
|
|
|
|
|
|
|
|
// 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 |
|
|
|
|
// into smaller chunks of sub-zones so they can be load balanced |
|
|
|
|
// independently. |
|
|
|
|
string sub_zone = 3; |
|
|
|
|
} |
|
|
|
|
|
|
|
|
|
// Identifies a specific Envoy instance. Remote server may have per Envoy configuration. |
|
|
|
|
// 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. |
|
|
|
|
message Node { |
|
|
|
|
// An opaque node identifier for the Envoy node. This must be set. |
|
|
|
|
string id = 1; |
|
|
|
|
// The cluster that the Envoy node belongs to. This must be set. |
|
|
|
|
string cluster = 2; |
|
|
|
|
// An opaque node identifier for the Envoy node. |
|
|
|
|
string id = 1 [(validate.rules).string.min_len = 1]; |
|
|
|
|
// The cluster that the Envoy node belongs to. |
|
|
|
|
string cluster = 2 [(validate.rules).string.min_len = 1]; |
|
|
|
|
// Opaque metadata extending the node identifier. Envoy will pass this |
|
|
|
|
// directly to the management server. |
|
|
|
|
google.protobuf.Struct metadata = 3; |
|
|
|
|
// Locality specifying where the Envoy instance is running. |
|
|
|
|
Locality locality = 4; |
|
|
|
|
// This is motivated by informing a management server during canary which |
|
|
|
|
// version of Envoy is being tested in a heterogeneous fleet. |
|
|
|
|
// version of Envoy is being tested in a heterogeneous fleet. This will be set |
|
|
|
|
// by Envoy in management server RPCs. |
|
|
|
|
string build_version = 5; |
|
|
|
|
} |
|
|
|
|
|
|
|
|
|
// Upstream host identifier. |
|
|
|
|
message Endpoint { |
|
|
|
|
Address address = 1; |
|
|
|
|
} |
|
|
|
@ -57,11 +69,12 @@ message Endpoint { |
|
|
|
|
// 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 |
|
|
|
|
// * ``{"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. |
|
|
|
|
message Metadata { |
|
|
|
|
// Key is the reverse DNS filter name. |
|
|
|
|
// Key is the reverse DNS filter name, e.g. com.acme.widget. The envoy.* |
|
|
|
|
// namespace is reserved for Envoy's built-in filters. |
|
|
|
|
map<string, google.protobuf.Struct> filter_metadata = 1; |
|
|
|
|
} |
|
|
|
|
|
|
|
|
@ -74,7 +87,8 @@ message RuntimeUInt32 { |
|
|
|
|
string runtime_key = 3; |
|
|
|
|
} |
|
|
|
|
|
|
|
|
|
// Envoy supports upstream priority routing both at the route and the virtual |
|
|
|
|
// Envoy supports :ref:`upstream priority routing |
|
|
|
|
// <arch_overview_http_routing_priority>` 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 |
|
|
|
@ -85,7 +99,7 @@ enum RoutingPriority { |
|
|
|
|
HIGH = 1; |
|
|
|
|
} |
|
|
|
|
|
|
|
|
|
// HTTP request method |
|
|
|
|
// HTTP request method. |
|
|
|
|
enum RequestMethod { |
|
|
|
|
METHOD_UNSPECIFIED = 0; |
|
|
|
|
GET = 1; |
|
|
|
@ -104,61 +118,78 @@ message HeaderValue { |
|
|
|
|
string key = 1; |
|
|
|
|
|
|
|
|
|
// Header value. |
|
|
|
|
// |
|
|
|
|
// The same :ref:`format specifier <config_access_log_format>` as used for |
|
|
|
|
// :ref:`HTTP access logging <config_access_log>` applies here, however |
|
|
|
|
// unknown header values are replaced with the empty string instead of `-`. |
|
|
|
|
string value = 2; |
|
|
|
|
} |
|
|
|
|
|
|
|
|
|
// Header name/value pair plus option to control append behavior. |
|
|
|
|
message HeaderValueOption { |
|
|
|
|
// Header Name/Value pair that this option applies to. |
|
|
|
|
// |
|
|
|
|
// The same format specifier as used for HTTP access logging applies here, |
|
|
|
|
// however unknown header values are replaced with the empty string instead |
|
|
|
|
// of -. [V2-API-DIFF]. |
|
|
|
|
// Header name/value pair that this option applies to. |
|
|
|
|
HeaderValue header = 1; |
|
|
|
|
|
|
|
|
|
// Should the value be appended? If true (default), the value is appended to |
|
|
|
|
// existing values [V2-API-DIFF]. |
|
|
|
|
// existing values. |
|
|
|
|
google.protobuf.BoolValue append = 2; |
|
|
|
|
} |
|
|
|
|
|
|
|
|
|
// API configuration source. This identifies the API type and cluster that Envoy |
|
|
|
|
// will use to fetch an xDS API. |
|
|
|
|
message ApiConfigSource { |
|
|
|
|
// APIs may be fetched via either REST or gRPC. |
|
|
|
|
enum ApiType { |
|
|
|
|
// REST legacy corresponds to the v1 API. |
|
|
|
|
// REST-JSON legacy corresponds to the v1 API. |
|
|
|
|
REST_LEGACY = 0; |
|
|
|
|
// REST-JSON v2 API. The `canonical JSON encoding |
|
|
|
|
// <https://developers.google.com/protocol-buffers/docs/proto3#json>`_ for |
|
|
|
|
// the v2 protos is used. |
|
|
|
|
REST = 1; |
|
|
|
|
// gRPC v2 API. |
|
|
|
|
GRPC = 2; |
|
|
|
|
} |
|
|
|
|
ApiType api_type = 1; |
|
|
|
|
// Multiple cluster names may be provided. If > 1 cluster is defined, clusters |
|
|
|
|
// will be cycled through if any kind of failure occurs. |
|
|
|
|
repeated string cluster_name = 2; |
|
|
|
|
repeated string cluster_name = 2 [(validate.rules).repeated.min_items = 1]; |
|
|
|
|
// For REST APIs, the delay between successive polls. |
|
|
|
|
google.protobuf.Duration refresh_delay = 3; |
|
|
|
|
} |
|
|
|
|
|
|
|
|
|
// ADS will be used to fetch resources. |
|
|
|
|
// Aggregated Discovery Service (ADS) options. This is currently empty, but when |
|
|
|
|
// set in :ref:`ConfigSource <envoy_api_msg_ConfigSource>` can be used to |
|
|
|
|
// specify that ADS is to be used. |
|
|
|
|
message AggregatedConfigSource { |
|
|
|
|
} |
|
|
|
|
|
|
|
|
|
// Configuration for listeners, clusters, routes, endpoints etc. may either be |
|
|
|
|
// sourced from the filesystem or from an API source. Filesystem configs are |
|
|
|
|
// watched with inotify for updates. |
|
|
|
|
// Configuration for :ref:`listeners <config_listeners>`, :ref:`clusters |
|
|
|
|
// <config_cluster_manager_cluster>`, :ref:`routes |
|
|
|
|
// <config_http_conn_man_route_table>`, :ref:`endpoints |
|
|
|
|
// <arch_overview_service_discovery>` etc. may either be sourced from the |
|
|
|
|
// filesystem or from an xDS API source. Filesystem configs are watched with |
|
|
|
|
// inotify for updates. |
|
|
|
|
message ConfigSource { |
|
|
|
|
oneof config_source_specifier { |
|
|
|
|
option (validate.required) = true; |
|
|
|
|
// Path on the filesystem to source and watch for configuration updates. |
|
|
|
|
string path = 1; |
|
|
|
|
// API configuration source. |
|
|
|
|
ApiConfigSource api_config_source = 2; |
|
|
|
|
// When set, ADS will be used to fetch resources. The ADS API configuration |
|
|
|
|
// source in the bootstrap configuration is used. |
|
|
|
|
AggregatedConfigSource ads = 3; |
|
|
|
|
} |
|
|
|
|
} |
|
|
|
|
|
|
|
|
|
// Configuration for transport socket in listeners and clusters. If the configuration is empty, |
|
|
|
|
// a default transport socket implementation and configuration will be chosen based on the |
|
|
|
|
// platform and existence of tls_context. |
|
|
|
|
// Configuration for transport socket in :ref:`listeners <config_listeners>` and |
|
|
|
|
// :ref:`clusters <config_cluster_manager_cluster>`. If the configuration is |
|
|
|
|
// empty, a default transport socket implementation and configuration will be |
|
|
|
|
// chosen based on the platform and existence of tls_context. |
|
|
|
|
message TransportSocket { |
|
|
|
|
// The name of the transport socket to instantiate. The name must match a supported transport |
|
|
|
|
// socket implementation. |
|
|
|
|
string name = 1; |
|
|
|
|
string name = 1 [(validate.rules).string.min_len = 1]; |
|
|
|
|
|
|
|
|
|
// Implementation specific configuration which depends on the implementation being instantiated. |
|
|
|
|
// See the supported transport socket implementations for further documentation. |
|
|
|
|