Package auth is a generated protocol buffer package.

Package cluster is a generated protocol buffer package.

Package core is a generated protocol buffer package.

Package endpoint is a generated protocol buffer package.

Package listener is a generated protocol buffer package.

Package ratelimit is a generated protocol buffer package.

Package route is a generated protocol buffer package.

Refer to the :ref:`service discovery type<arch_overview_service_discovery_types_sds>` for an explanation.

Refer to the :ref:`least request load balancing policy<arch_overview_load_balancing_types_least_request>` for an explanation.

Refer to the :ref:`logical DNS discovery type<arch_overview_service_discovery_types_logical_dns>` for an explanation.

Refer to the :ref:`Maglev load balancing policy<arch_overview_load_balancing_types_maglev>` for an explanation.

Refer to the :ref:`original destination discovery type<arch_overview_service_discovery_types_original_destination>` for an explanation.

Refer to the :ref:`original destination load balancing policy<arch_overview_load_balancing_types_original_destination>` for an explanation.

Refer to the :ref:`random load balancing policy<arch_overview_load_balancing_types_random>` for an explanation.

Refer to the :ref:`ring hash load balancing policy<arch_overview_load_balancing_types_ring_hash>` for an explanation.

Refer to the :ref:`round robin load balancing policy<arch_overview_load_balancing_types_round_robin>` for an explanation.

Refer to the :ref:`static discovery type<arch_overview_service_discovery_types_static>` for an explanation.

Refer to the :ref:`strict DNS discovery type<arch_overview_service_discovery_types_strict_dns>` for an explanation.

Cluster can only operate on one of the possible upstream protocols (HTTP1.1, HTTP2).

Use HTTP1.1 or HTTP2, depending on which one is used on the downstream connection.

Drain in response to calling /healthcheck/fail admin endpoint (along with the health check filter), listener removal/modification, and hot restart.

Drain in response to listener removal/modification and hot restart.

Configuration for a single upstream cluster.

Common configuration for all load balancer implementations.

[#not-implemented-hide:].

Only valid when discovery type is EDS.

Optionally divide the endpoints in this cluster into subsets defined by endpoint metadata and selected by route and weighted cluster metadata.

Specifications for subsets.

Specific configuration for the :ref:`RingHash<arch_overview_load_balancing_types_ring_hash>` load balancing policy.

[#not-implemented-hide:] Hide from docs.

Each route from RDS will map to a single cluster or traffic split across clusters using weights expressed in the RDS WeightedCluster.

Load balancing policy settings.

A DiscoveryRequest requests a set of versioned resources of the same type for a given Envoy node on some API.

[#not-implemented-hide:].

An extensible structure containing the address Envoy should bind to when establishing upstream connections.

Refer to :ref:`service discovery type <arch_overview_service_discovery_types>` for an explanation on each type.

When V4_ONLY is selected, the DNS resolver will only perform a lookup for addresses in the IPv4 family.

Refer to :ref:`load balancer type <arch_overview_load_balancing_types>` architecture overview section for information on each type.

If NO_FALLBACK is selected, a result equivalent to no healthy hosts is reported.