public static final class Cluster.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder> implements ClusterOrBuilder
Configuration for a single upstream cluster. [#next-free-field: 53]Protobuf type
envoy.config.cluster.v4alpha.Cluster| Modifier and Type | Method and Description |
|---|---|
Cluster.Builder |
addAllDnsResolvers(Iterable<? extends Address> values)
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
Cluster.Builder |
addAllFilters(Iterable<? extends Filter> values)
An (optional) network filter chain, listed in the order the filters should be applied.
|
Cluster.Builder |
addAllHealthChecks(Iterable<? extends HealthCheck> values)
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
Cluster.Builder |
addAllTransportSocketMatches(Iterable<? extends Cluster.TransportSocketMatch> values)
Configuration to use different transport sockets for different endpoints.
|
Cluster.Builder |
addDnsResolvers(Address.Builder builderForValue)
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
Cluster.Builder |
addDnsResolvers(Address value)
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
Cluster.Builder |
addDnsResolvers(int index,
Address.Builder builderForValue)
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
Cluster.Builder |
addDnsResolvers(int index,
Address value)
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
Address.Builder |
addDnsResolversBuilder()
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
Address.Builder |
addDnsResolversBuilder(int index)
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
Cluster.Builder |
addFilters(Filter.Builder builderForValue)
An (optional) network filter chain, listed in the order the filters should be applied.
|
Cluster.Builder |
addFilters(Filter value)
An (optional) network filter chain, listed in the order the filters should be applied.
|
Cluster.Builder |
addFilters(int index,
Filter.Builder builderForValue)
An (optional) network filter chain, listed in the order the filters should be applied.
|
Cluster.Builder |
addFilters(int index,
Filter value)
An (optional) network filter chain, listed in the order the filters should be applied.
|
Filter.Builder |
addFiltersBuilder()
An (optional) network filter chain, listed in the order the filters should be applied.
|
Filter.Builder |
addFiltersBuilder(int index)
An (optional) network filter chain, listed in the order the filters should be applied.
|
Cluster.Builder |
addHealthChecks(HealthCheck.Builder builderForValue)
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
Cluster.Builder |
addHealthChecks(HealthCheck value)
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
Cluster.Builder |
addHealthChecks(int index,
HealthCheck.Builder builderForValue)
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
Cluster.Builder |
addHealthChecks(int index,
HealthCheck value)
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
HealthCheck.Builder |
addHealthChecksBuilder()
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
HealthCheck.Builder |
addHealthChecksBuilder(int index)
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
Cluster.Builder |
addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field,
Object value) |
Cluster.Builder |
addTransportSocketMatches(Cluster.TransportSocketMatch.Builder builderForValue)
Configuration to use different transport sockets for different endpoints.
|
Cluster.Builder |
addTransportSocketMatches(Cluster.TransportSocketMatch value)
Configuration to use different transport sockets for different endpoints.
|
Cluster.Builder |
addTransportSocketMatches(int index,
Cluster.TransportSocketMatch.Builder builderForValue)
Configuration to use different transport sockets for different endpoints.
|
Cluster.Builder |
addTransportSocketMatches(int index,
Cluster.TransportSocketMatch value)
Configuration to use different transport sockets for different endpoints.
|
Cluster.TransportSocketMatch.Builder |
addTransportSocketMatchesBuilder()
Configuration to use different transport sockets for different endpoints.
|
Cluster.TransportSocketMatch.Builder |
addTransportSocketMatchesBuilder(int index)
Configuration to use different transport sockets for different endpoints.
|
Cluster |
build() |
Cluster |
buildPartial() |
Cluster.Builder |
clear() |
Cluster.Builder |
clearAltStatName()
An optional alternative to the cluster name to be used while emitting stats.
|
Cluster.Builder |
clearCircuitBreakers()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
|
Cluster.Builder |
clearCleanupInterval()
The interval for removing stale hosts from a cluster type
:ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`.
|
Cluster.Builder |
clearCloseConnectionsOnHostHealthFailure()
If an upstream host becomes unhealthy (as determined by the configured health checks
or outlier detection), immediately close all connections to the failed host.
.. note::
This is currently only supported for connections created by tcp_proxy.
.. note::
The current implementation of this feature closes all connections immediately when
the unhealthy status is detected.
|
Cluster.Builder |
clearClusterDiscoveryType() |
Cluster.Builder |
clearClusterType()
The custom cluster type.
|
Cluster.Builder |
clearCommonLbConfig()
Common configuration for all load balancer implementations.
|
Cluster.Builder |
clearConnectionPoolPerDownstreamConnection()
If `connection_pool_per_downstream_connection` is true, the cluster will use a separate
connection pool for every downstream connection
bool connection_pool_per_downstream_connection = 51; |
Cluster.Builder |
clearConnectTimeout()
The timeout for new network connections to hosts in the cluster.
|
Cluster.Builder |
clearDnsFailureRefreshRate()
If the DNS failure refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this is used as the cluster’s DNS refresh rate when requests are failing.
|
Cluster.Builder |
clearDnsLookupFamily()
The DNS IP address resolution policy.
|
Cluster.Builder |
clearDnsRefreshRate()
If the DNS refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used as the cluster’s DNS refresh
rate.
|
Cluster.Builder |
clearDnsResolvers()
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
Cluster.Builder |
clearEdsClusterConfig()
Configuration to use for EDS updates for the Cluster.
|
Cluster.Builder |
clearField(com.google.protobuf.Descriptors.FieldDescriptor field) |
Cluster.Builder |
clearFilters()
An (optional) network filter chain, listed in the order the filters should be applied.
|
Cluster.Builder |
clearHealthChecks()
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
Cluster.Builder |
clearIgnoreHealthOnHostRemoval()
If set to true, Envoy will ignore the health value of a host when processing its removal
from service discovery.
|
Cluster.Builder |
clearLbConfig() |
Cluster.Builder |
clearLbPolicy()
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use
when picking a host in the cluster.
|
Cluster.Builder |
clearLbSubsetConfig()
Configuration for load balancing subsetting.
|
Cluster.Builder |
clearLeastRequestLbConfig()
Optional configuration for the LeastRequest load balancing policy.
|
Cluster.Builder |
clearLoadAssignment()
Setting this is required for specifying members of
:ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`,
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.
|
Cluster.Builder |
clearLoadBalancingPolicy()
[#not-implemented-hide:] New mechanism for LB policy configuration.
|
Cluster.Builder |
clearLrsServer()
[#not-implemented-hide:]
If present, tells the client where to send load reports via LRS.
|
Cluster.Builder |
clearMaglevLbConfig()
Optional configuration for the Maglev load balancing policy.
|
Cluster.Builder |
clearMaxRequestsPerConnection()
Optional maximum requests for a single upstream connection.
|
Cluster.Builder |
clearMetadata()
The Metadata field can be used to provide additional information about the
cluster.
|
Cluster.Builder |
clearName()
Supplies the name of the cluster which must be unique across all clusters.
|
Cluster.Builder |
clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof) |
Cluster.Builder |
clearOriginalDstLbConfig()
Optional configuration for the Original Destination load balancing policy.
|
Cluster.Builder |
clearOutlierDetection()
If specified, outlier detection will be enabled for this upstream cluster.
|
Cluster.Builder |
clearPerConnectionBufferLimitBytes()
Soft limit on size of the cluster’s connections read and write buffers.
|
Cluster.Builder |
clearPreconnectPolicy()
[#not-implemented-hide:]
Preconnect configuration for this cluster.
|
Cluster.Builder |
clearRespectDnsTtl()
Optional configuration for setting cluster's DNS refresh rate.
|
Cluster.Builder |
clearRingHashLbConfig()
Optional configuration for the Ring Hash load balancing policy.
|
Cluster.Builder |
clearTrackClusterStats()
Configuration to track optional cluster stats.
|
Cluster.Builder |
clearTransportSocket()
Optional custom transport socket implementation to use for upstream connections.
|
Cluster.Builder |
clearTransportSocketMatches()
Configuration to use different transport sockets for different endpoints.
|
Cluster.Builder |
clearType()
The :ref:`service discovery type <arch_overview_service_discovery_types>`
to use for resolving the cluster.
|
Cluster.Builder |
clearTypedExtensionProtocolOptions() |
Cluster.Builder |
clearUpstreamBindConfig()
Optional configuration used to bind newly established upstream connections.
|
Cluster.Builder |
clearUpstreamConfig()
Optional customization and configuration of upstream connection pool, and upstream type.
|
Cluster.Builder |
clearUpstreamConnectionOptions()
Optional options for upstream connections.
|
Cluster.Builder |
clearUseTcpForDnsLookups()
[#next-major-version: Reconcile DNS options in a single message.]
|
Cluster.Builder |
clone() |
boolean |
containsTypedExtensionProtocolOptions(String key)
The extension_protocol_options field is used to provide extension-specific protocol options
for upstream connections.
|
String |
getAltStatName()
An optional alternative to the cluster name to be used while emitting stats.
|
com.google.protobuf.ByteString |
getAltStatNameBytes()
An optional alternative to the cluster name to be used while emitting stats.
|
CircuitBreakers |
getCircuitBreakers()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
|
CircuitBreakers.Builder |
getCircuitBreakersBuilder()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
|
CircuitBreakersOrBuilder |
getCircuitBreakersOrBuilder()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
|
com.google.protobuf.Duration |
getCleanupInterval()
The interval for removing stale hosts from a cluster type
:ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`.
|
com.google.protobuf.Duration.Builder |
getCleanupIntervalBuilder()
The interval for removing stale hosts from a cluster type
:ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`.
|
com.google.protobuf.DurationOrBuilder |
getCleanupIntervalOrBuilder()
The interval for removing stale hosts from a cluster type
:ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`.
|
boolean |
getCloseConnectionsOnHostHealthFailure()
If an upstream host becomes unhealthy (as determined by the configured health checks
or outlier detection), immediately close all connections to the failed host.
.. note::
This is currently only supported for connections created by tcp_proxy.
.. note::
The current implementation of this feature closes all connections immediately when
the unhealthy status is detected.
|
Cluster.ClusterDiscoveryTypeCase |
getClusterDiscoveryTypeCase() |
Cluster.CustomClusterType |
getClusterType()
The custom cluster type.
|
Cluster.CustomClusterType.Builder |
getClusterTypeBuilder()
The custom cluster type.
|
Cluster.CustomClusterTypeOrBuilder |
getClusterTypeOrBuilder()
The custom cluster type.
|
Cluster.CommonLbConfig |
getCommonLbConfig()
Common configuration for all load balancer implementations.
|
Cluster.CommonLbConfig.Builder |
getCommonLbConfigBuilder()
Common configuration for all load balancer implementations.
|
Cluster.CommonLbConfigOrBuilder |
getCommonLbConfigOrBuilder()
Common configuration for all load balancer implementations.
|
boolean |
getConnectionPoolPerDownstreamConnection()
If `connection_pool_per_downstream_connection` is true, the cluster will use a separate
connection pool for every downstream connection
bool connection_pool_per_downstream_connection = 51; |
com.google.protobuf.Duration |
getConnectTimeout()
The timeout for new network connections to hosts in the cluster.
|
com.google.protobuf.Duration.Builder |
getConnectTimeoutBuilder()
The timeout for new network connections to hosts in the cluster.
|
com.google.protobuf.DurationOrBuilder |
getConnectTimeoutOrBuilder()
The timeout for new network connections to hosts in the cluster.
|
Cluster |
getDefaultInstanceForType() |
static com.google.protobuf.Descriptors.Descriptor |
getDescriptor() |
com.google.protobuf.Descriptors.Descriptor |
getDescriptorForType() |
Cluster.RefreshRate |
getDnsFailureRefreshRate()
If the DNS failure refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this is used as the cluster’s DNS refresh rate when requests are failing.
|
Cluster.RefreshRate.Builder |
getDnsFailureRefreshRateBuilder()
If the DNS failure refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this is used as the cluster’s DNS refresh rate when requests are failing.
|
Cluster.RefreshRateOrBuilder |
getDnsFailureRefreshRateOrBuilder()
If the DNS failure refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this is used as the cluster’s DNS refresh rate when requests are failing.
|
Cluster.DnsLookupFamily |
getDnsLookupFamily()
The DNS IP address resolution policy.
|
int |
getDnsLookupFamilyValue()
The DNS IP address resolution policy.
|
com.google.protobuf.Duration |
getDnsRefreshRate()
If the DNS refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used as the cluster’s DNS refresh
rate.
|
com.google.protobuf.Duration.Builder |
getDnsRefreshRateBuilder()
If the DNS refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used as the cluster’s DNS refresh
rate.
|
com.google.protobuf.DurationOrBuilder |
getDnsRefreshRateOrBuilder()
If the DNS refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used as the cluster’s DNS refresh
rate.
|
Address |
getDnsResolvers(int index)
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
Address.Builder |
getDnsResolversBuilder(int index)
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
List<Address.Builder> |
getDnsResolversBuilderList()
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
int |
getDnsResolversCount()
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
List<Address> |
getDnsResolversList()
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
AddressOrBuilder |
getDnsResolversOrBuilder(int index)
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
List<? extends AddressOrBuilder> |
getDnsResolversOrBuilderList()
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
Cluster.EdsClusterConfig |
getEdsClusterConfig()
Configuration to use for EDS updates for the Cluster.
|
Cluster.EdsClusterConfig.Builder |
getEdsClusterConfigBuilder()
Configuration to use for EDS updates for the Cluster.
|
Cluster.EdsClusterConfigOrBuilder |
getEdsClusterConfigOrBuilder()
Configuration to use for EDS updates for the Cluster.
|
Filter |
getFilters(int index)
An (optional) network filter chain, listed in the order the filters should be applied.
|
Filter.Builder |
getFiltersBuilder(int index)
An (optional) network filter chain, listed in the order the filters should be applied.
|
List<Filter.Builder> |
getFiltersBuilderList()
An (optional) network filter chain, listed in the order the filters should be applied.
|
int |
getFiltersCount()
An (optional) network filter chain, listed in the order the filters should be applied.
|
List<Filter> |
getFiltersList()
An (optional) network filter chain, listed in the order the filters should be applied.
|
FilterOrBuilder |
getFiltersOrBuilder(int index)
An (optional) network filter chain, listed in the order the filters should be applied.
|
List<? extends FilterOrBuilder> |
getFiltersOrBuilderList()
An (optional) network filter chain, listed in the order the filters should be applied.
|
HealthCheck |
getHealthChecks(int index)
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
HealthCheck.Builder |
getHealthChecksBuilder(int index)
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
List<HealthCheck.Builder> |
getHealthChecksBuilderList()
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
int |
getHealthChecksCount()
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
List<HealthCheck> |
getHealthChecksList()
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
HealthCheckOrBuilder |
getHealthChecksOrBuilder(int index)
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
List<? extends HealthCheckOrBuilder> |
getHealthChecksOrBuilderList()
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
boolean |
getIgnoreHealthOnHostRemoval()
If set to true, Envoy will ignore the health value of a host when processing its removal
from service discovery.
|
Cluster.LbConfigCase |
getLbConfigCase() |
Cluster.LbPolicy |
getLbPolicy()
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use
when picking a host in the cluster.
|
int |
getLbPolicyValue()
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use
when picking a host in the cluster.
|
Cluster.LbSubsetConfig |
getLbSubsetConfig()
Configuration for load balancing subsetting.
|
Cluster.LbSubsetConfig.Builder |
getLbSubsetConfigBuilder()
Configuration for load balancing subsetting.
|
Cluster.LbSubsetConfigOrBuilder |
getLbSubsetConfigOrBuilder()
Configuration for load balancing subsetting.
|
Cluster.LeastRequestLbConfig |
getLeastRequestLbConfig()
Optional configuration for the LeastRequest load balancing policy.
|
Cluster.LeastRequestLbConfig.Builder |
getLeastRequestLbConfigBuilder()
Optional configuration for the LeastRequest load balancing policy.
|
Cluster.LeastRequestLbConfigOrBuilder |
getLeastRequestLbConfigOrBuilder()
Optional configuration for the LeastRequest load balancing policy.
|
ClusterLoadAssignment |
getLoadAssignment()
Setting this is required for specifying members of
:ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`,
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.
|
ClusterLoadAssignment.Builder |
getLoadAssignmentBuilder()
Setting this is required for specifying members of
:ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`,
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.
|
ClusterLoadAssignmentOrBuilder |
getLoadAssignmentOrBuilder()
Setting this is required for specifying members of
:ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`,
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.
|
LoadBalancingPolicy |
getLoadBalancingPolicy()
[#not-implemented-hide:] New mechanism for LB policy configuration.
|
LoadBalancingPolicy.Builder |
getLoadBalancingPolicyBuilder()
[#not-implemented-hide:] New mechanism for LB policy configuration.
|
LoadBalancingPolicyOrBuilder |
getLoadBalancingPolicyOrBuilder()
[#not-implemented-hide:] New mechanism for LB policy configuration.
|
ConfigSource |
getLrsServer()
[#not-implemented-hide:]
If present, tells the client where to send load reports via LRS.
|
ConfigSource.Builder |
getLrsServerBuilder()
[#not-implemented-hide:]
If present, tells the client where to send load reports via LRS.
|
ConfigSourceOrBuilder |
getLrsServerOrBuilder()
[#not-implemented-hide:]
If present, tells the client where to send load reports via LRS.
|
Cluster.MaglevLbConfig |
getMaglevLbConfig()
Optional configuration for the Maglev load balancing policy.
|
Cluster.MaglevLbConfig.Builder |
getMaglevLbConfigBuilder()
Optional configuration for the Maglev load balancing policy.
|
Cluster.MaglevLbConfigOrBuilder |
getMaglevLbConfigOrBuilder()
Optional configuration for the Maglev load balancing policy.
|
com.google.protobuf.UInt32Value |
getMaxRequestsPerConnection()
Optional maximum requests for a single upstream connection.
|
com.google.protobuf.UInt32Value.Builder |
getMaxRequestsPerConnectionBuilder()
Optional maximum requests for a single upstream connection.
|
com.google.protobuf.UInt32ValueOrBuilder |
getMaxRequestsPerConnectionOrBuilder()
Optional maximum requests for a single upstream connection.
|
Metadata |
getMetadata()
The Metadata field can be used to provide additional information about the
cluster.
|
Metadata.Builder |
getMetadataBuilder()
The Metadata field can be used to provide additional information about the
cluster.
|
MetadataOrBuilder |
getMetadataOrBuilder()
The Metadata field can be used to provide additional information about the
cluster.
|
Map<String,com.google.protobuf.Any> |
getMutableTypedExtensionProtocolOptions()
Deprecated.
|
String |
getName()
Supplies the name of the cluster which must be unique across all clusters.
|
com.google.protobuf.ByteString |
getNameBytes()
Supplies the name of the cluster which must be unique across all clusters.
|
Cluster.OriginalDstLbConfig |
getOriginalDstLbConfig()
Optional configuration for the Original Destination load balancing policy.
|
Cluster.OriginalDstLbConfig.Builder |
getOriginalDstLbConfigBuilder()
Optional configuration for the Original Destination load balancing policy.
|
Cluster.OriginalDstLbConfigOrBuilder |
getOriginalDstLbConfigOrBuilder()
Optional configuration for the Original Destination load balancing policy.
|
OutlierDetection |
getOutlierDetection()
If specified, outlier detection will be enabled for this upstream cluster.
|
OutlierDetection.Builder |
getOutlierDetectionBuilder()
If specified, outlier detection will be enabled for this upstream cluster.
|
OutlierDetectionOrBuilder |
getOutlierDetectionOrBuilder()
If specified, outlier detection will be enabled for this upstream cluster.
|
com.google.protobuf.UInt32Value |
getPerConnectionBufferLimitBytes()
Soft limit on size of the cluster’s connections read and write buffers.
|
com.google.protobuf.UInt32Value.Builder |
getPerConnectionBufferLimitBytesBuilder()
Soft limit on size of the cluster’s connections read and write buffers.
|
com.google.protobuf.UInt32ValueOrBuilder |
getPerConnectionBufferLimitBytesOrBuilder()
Soft limit on size of the cluster’s connections read and write buffers.
|
Cluster.PreconnectPolicy |
getPreconnectPolicy()
[#not-implemented-hide:]
Preconnect configuration for this cluster.
|
Cluster.PreconnectPolicy.Builder |
getPreconnectPolicyBuilder()
[#not-implemented-hide:]
Preconnect configuration for this cluster.
|
Cluster.PreconnectPolicyOrBuilder |
getPreconnectPolicyOrBuilder()
[#not-implemented-hide:]
Preconnect configuration for this cluster.
|
boolean |
getRespectDnsTtl()
Optional configuration for setting cluster's DNS refresh rate.
|
Cluster.RingHashLbConfig |
getRingHashLbConfig()
Optional configuration for the Ring Hash load balancing policy.
|
Cluster.RingHashLbConfig.Builder |
getRingHashLbConfigBuilder()
Optional configuration for the Ring Hash load balancing policy.
|
Cluster.RingHashLbConfigOrBuilder |
getRingHashLbConfigOrBuilder()
Optional configuration for the Ring Hash load balancing policy.
|
TrackClusterStats |
getTrackClusterStats()
Configuration to track optional cluster stats.
|
TrackClusterStats.Builder |
getTrackClusterStatsBuilder()
Configuration to track optional cluster stats.
|
TrackClusterStatsOrBuilder |
getTrackClusterStatsOrBuilder()
Configuration to track optional cluster stats.
|
TransportSocket |
getTransportSocket()
Optional custom transport socket implementation to use for upstream connections.
|
TransportSocket.Builder |
getTransportSocketBuilder()
Optional custom transport socket implementation to use for upstream connections.
|
Cluster.TransportSocketMatch |
getTransportSocketMatches(int index)
Configuration to use different transport sockets for different endpoints.
|
Cluster.TransportSocketMatch.Builder |
getTransportSocketMatchesBuilder(int index)
Configuration to use different transport sockets for different endpoints.
|
List<Cluster.TransportSocketMatch.Builder> |
getTransportSocketMatchesBuilderList()
Configuration to use different transport sockets for different endpoints.
|
int |
getTransportSocketMatchesCount()
Configuration to use different transport sockets for different endpoints.
|
List<Cluster.TransportSocketMatch> |
getTransportSocketMatchesList()
Configuration to use different transport sockets for different endpoints.
|
Cluster.TransportSocketMatchOrBuilder |
getTransportSocketMatchesOrBuilder(int index)
Configuration to use different transport sockets for different endpoints.
|
List<? extends Cluster.TransportSocketMatchOrBuilder> |
getTransportSocketMatchesOrBuilderList()
Configuration to use different transport sockets for different endpoints.
|
TransportSocketOrBuilder |
getTransportSocketOrBuilder()
Optional custom transport socket implementation to use for upstream connections.
|
Cluster.DiscoveryType |
getType()
The :ref:`service discovery type <arch_overview_service_discovery_types>`
to use for resolving the cluster.
|
Map<String,com.google.protobuf.Any> |
getTypedExtensionProtocolOptions()
Deprecated.
|
int |
getTypedExtensionProtocolOptionsCount()
The extension_protocol_options field is used to provide extension-specific protocol options
for upstream connections.
|
Map<String,com.google.protobuf.Any> |
getTypedExtensionProtocolOptionsMap()
The extension_protocol_options field is used to provide extension-specific protocol options
for upstream connections.
|
com.google.protobuf.Any |
getTypedExtensionProtocolOptionsOrDefault(String key,
com.google.protobuf.Any defaultValue)
The extension_protocol_options field is used to provide extension-specific protocol options
for upstream connections.
|
com.google.protobuf.Any |
getTypedExtensionProtocolOptionsOrThrow(String key)
The extension_protocol_options field is used to provide extension-specific protocol options
for upstream connections.
|
int |
getTypeValue()
The :ref:`service discovery type <arch_overview_service_discovery_types>`
to use for resolving the cluster.
|
BindConfig |
getUpstreamBindConfig()
Optional configuration used to bind newly established upstream connections.
|
BindConfig.Builder |
getUpstreamBindConfigBuilder()
Optional configuration used to bind newly established upstream connections.
|
BindConfigOrBuilder |
getUpstreamBindConfigOrBuilder()
Optional configuration used to bind newly established upstream connections.
|
TypedExtensionConfig |
getUpstreamConfig()
Optional customization and configuration of upstream connection pool, and upstream type.
|
TypedExtensionConfig.Builder |
getUpstreamConfigBuilder()
Optional customization and configuration of upstream connection pool, and upstream type.
|
TypedExtensionConfigOrBuilder |
getUpstreamConfigOrBuilder()
Optional customization and configuration of upstream connection pool, and upstream type.
|
UpstreamConnectionOptions |
getUpstreamConnectionOptions()
Optional options for upstream connections.
|
UpstreamConnectionOptions.Builder |
getUpstreamConnectionOptionsBuilder()
Optional options for upstream connections.
|
UpstreamConnectionOptionsOrBuilder |
getUpstreamConnectionOptionsOrBuilder()
Optional options for upstream connections.
|
boolean |
getUseTcpForDnsLookups()
[#next-major-version: Reconcile DNS options in a single message.]
|
boolean |
hasCircuitBreakers()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
|
boolean |
hasCleanupInterval()
The interval for removing stale hosts from a cluster type
:ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`.
|
boolean |
hasClusterType()
The custom cluster type.
|
boolean |
hasCommonLbConfig()
Common configuration for all load balancer implementations.
|
boolean |
hasConnectTimeout()
The timeout for new network connections to hosts in the cluster.
|
boolean |
hasDnsFailureRefreshRate()
If the DNS failure refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this is used as the cluster’s DNS refresh rate when requests are failing.
|
boolean |
hasDnsRefreshRate()
If the DNS refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used as the cluster’s DNS refresh
rate.
|
boolean |
hasEdsClusterConfig()
Configuration to use for EDS updates for the Cluster.
|
boolean |
hasLbSubsetConfig()
Configuration for load balancing subsetting.
|
boolean |
hasLeastRequestLbConfig()
Optional configuration for the LeastRequest load balancing policy.
|
boolean |
hasLoadAssignment()
Setting this is required for specifying members of
:ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`,
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.
|
boolean |
hasLoadBalancingPolicy()
[#not-implemented-hide:] New mechanism for LB policy configuration.
|
boolean |
hasLrsServer()
[#not-implemented-hide:]
If present, tells the client where to send load reports via LRS.
|
boolean |
hasMaglevLbConfig()
Optional configuration for the Maglev load balancing policy.
|
boolean |
hasMaxRequestsPerConnection()
Optional maximum requests for a single upstream connection.
|
boolean |
hasMetadata()
The Metadata field can be used to provide additional information about the
cluster.
|
boolean |
hasOriginalDstLbConfig()
Optional configuration for the Original Destination load balancing policy.
|
boolean |
hasOutlierDetection()
If specified, outlier detection will be enabled for this upstream cluster.
|
boolean |
hasPerConnectionBufferLimitBytes()
Soft limit on size of the cluster’s connections read and write buffers.
|
boolean |
hasPreconnectPolicy()
[#not-implemented-hide:]
Preconnect configuration for this cluster.
|
boolean |
hasRingHashLbConfig()
Optional configuration for the Ring Hash load balancing policy.
|
boolean |
hasTrackClusterStats()
Configuration to track optional cluster stats.
|
boolean |
hasTransportSocket()
Optional custom transport socket implementation to use for upstream connections.
|
boolean |
hasUpstreamBindConfig()
Optional configuration used to bind newly established upstream connections.
|
boolean |
hasUpstreamConfig()
Optional customization and configuration of upstream connection pool, and upstream type.
|
boolean |
hasUpstreamConnectionOptions()
Optional options for upstream connections.
|
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable |
internalGetFieldAccessorTable() |
protected com.google.protobuf.MapField |
internalGetMapField(int number) |
protected com.google.protobuf.MapField |
internalGetMutableMapField(int number) |
boolean |
isInitialized() |
Cluster.Builder |
mergeCircuitBreakers(CircuitBreakers value)
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
|
Cluster.Builder |
mergeCleanupInterval(com.google.protobuf.Duration value)
The interval for removing stale hosts from a cluster type
:ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`.
|
Cluster.Builder |
mergeClusterType(Cluster.CustomClusterType value)
The custom cluster type.
|
Cluster.Builder |
mergeCommonLbConfig(Cluster.CommonLbConfig value)
Common configuration for all load balancer implementations.
|
Cluster.Builder |
mergeConnectTimeout(com.google.protobuf.Duration value)
The timeout for new network connections to hosts in the cluster.
|
Cluster.Builder |
mergeDnsFailureRefreshRate(Cluster.RefreshRate value)
If the DNS failure refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this is used as the cluster’s DNS refresh rate when requests are failing.
|
Cluster.Builder |
mergeDnsRefreshRate(com.google.protobuf.Duration value)
If the DNS refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used as the cluster’s DNS refresh
rate.
|
Cluster.Builder |
mergeEdsClusterConfig(Cluster.EdsClusterConfig value)
Configuration to use for EDS updates for the Cluster.
|
Cluster.Builder |
mergeFrom(Cluster other) |
Cluster.Builder |
mergeFrom(com.google.protobuf.CodedInputStream input,
com.google.protobuf.ExtensionRegistryLite extensionRegistry) |
Cluster.Builder |
mergeFrom(com.google.protobuf.Message other) |
Cluster.Builder |
mergeLbSubsetConfig(Cluster.LbSubsetConfig value)
Configuration for load balancing subsetting.
|
Cluster.Builder |
mergeLeastRequestLbConfig(Cluster.LeastRequestLbConfig value)
Optional configuration for the LeastRequest load balancing policy.
|
Cluster.Builder |
mergeLoadAssignment(ClusterLoadAssignment value)
Setting this is required for specifying members of
:ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`,
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.
|
Cluster.Builder |
mergeLoadBalancingPolicy(LoadBalancingPolicy value)
[#not-implemented-hide:] New mechanism for LB policy configuration.
|
Cluster.Builder |
mergeLrsServer(ConfigSource value)
[#not-implemented-hide:]
If present, tells the client where to send load reports via LRS.
|
Cluster.Builder |
mergeMaglevLbConfig(Cluster.MaglevLbConfig value)
Optional configuration for the Maglev load balancing policy.
|
Cluster.Builder |
mergeMaxRequestsPerConnection(com.google.protobuf.UInt32Value value)
Optional maximum requests for a single upstream connection.
|
Cluster.Builder |
mergeMetadata(Metadata value)
The Metadata field can be used to provide additional information about the
cluster.
|
Cluster.Builder |
mergeOriginalDstLbConfig(Cluster.OriginalDstLbConfig value)
Optional configuration for the Original Destination load balancing policy.
|
Cluster.Builder |
mergeOutlierDetection(OutlierDetection value)
If specified, outlier detection will be enabled for this upstream cluster.
|
Cluster.Builder |
mergePerConnectionBufferLimitBytes(com.google.protobuf.UInt32Value value)
Soft limit on size of the cluster’s connections read and write buffers.
|
Cluster.Builder |
mergePreconnectPolicy(Cluster.PreconnectPolicy value)
[#not-implemented-hide:]
Preconnect configuration for this cluster.
|
Cluster.Builder |
mergeRingHashLbConfig(Cluster.RingHashLbConfig value)
Optional configuration for the Ring Hash load balancing policy.
|
Cluster.Builder |
mergeTrackClusterStats(TrackClusterStats value)
Configuration to track optional cluster stats.
|
Cluster.Builder |
mergeTransportSocket(TransportSocket value)
Optional custom transport socket implementation to use for upstream connections.
|
Cluster.Builder |
mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) |
Cluster.Builder |
mergeUpstreamBindConfig(BindConfig value)
Optional configuration used to bind newly established upstream connections.
|
Cluster.Builder |
mergeUpstreamConfig(TypedExtensionConfig value)
Optional customization and configuration of upstream connection pool, and upstream type.
|
Cluster.Builder |
mergeUpstreamConnectionOptions(UpstreamConnectionOptions value)
Optional options for upstream connections.
|
Cluster.Builder |
putAllTypedExtensionProtocolOptions(Map<String,com.google.protobuf.Any> values)
The extension_protocol_options field is used to provide extension-specific protocol options
for upstream connections.
|
Cluster.Builder |
putTypedExtensionProtocolOptions(String key,
com.google.protobuf.Any value)
The extension_protocol_options field is used to provide extension-specific protocol options
for upstream connections.
|
Cluster.Builder |
removeDnsResolvers(int index)
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
Cluster.Builder |
removeFilters(int index)
An (optional) network filter chain, listed in the order the filters should be applied.
|
Cluster.Builder |
removeHealthChecks(int index)
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
Cluster.Builder |
removeTransportSocketMatches(int index)
Configuration to use different transport sockets for different endpoints.
|
Cluster.Builder |
removeTypedExtensionProtocolOptions(String key)
The extension_protocol_options field is used to provide extension-specific protocol options
for upstream connections.
|
Cluster.Builder |
setAltStatName(String value)
An optional alternative to the cluster name to be used while emitting stats.
|
Cluster.Builder |
setAltStatNameBytes(com.google.protobuf.ByteString value)
An optional alternative to the cluster name to be used while emitting stats.
|
Cluster.Builder |
setCircuitBreakers(CircuitBreakers.Builder builderForValue)
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
|
Cluster.Builder |
setCircuitBreakers(CircuitBreakers value)
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
|
Cluster.Builder |
setCleanupInterval(com.google.protobuf.Duration.Builder builderForValue)
The interval for removing stale hosts from a cluster type
:ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`.
|
Cluster.Builder |
setCleanupInterval(com.google.protobuf.Duration value)
The interval for removing stale hosts from a cluster type
:ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`.
|
Cluster.Builder |
setCloseConnectionsOnHostHealthFailure(boolean value)
If an upstream host becomes unhealthy (as determined by the configured health checks
or outlier detection), immediately close all connections to the failed host.
.. note::
This is currently only supported for connections created by tcp_proxy.
.. note::
The current implementation of this feature closes all connections immediately when
the unhealthy status is detected.
|
Cluster.Builder |
setClusterType(Cluster.CustomClusterType.Builder builderForValue)
The custom cluster type.
|
Cluster.Builder |
setClusterType(Cluster.CustomClusterType value)
The custom cluster type.
|
Cluster.Builder |
setCommonLbConfig(Cluster.CommonLbConfig.Builder builderForValue)
Common configuration for all load balancer implementations.
|
Cluster.Builder |
setCommonLbConfig(Cluster.CommonLbConfig value)
Common configuration for all load balancer implementations.
|
Cluster.Builder |
setConnectionPoolPerDownstreamConnection(boolean value)
If `connection_pool_per_downstream_connection` is true, the cluster will use a separate
connection pool for every downstream connection
bool connection_pool_per_downstream_connection = 51; |
Cluster.Builder |
setConnectTimeout(com.google.protobuf.Duration.Builder builderForValue)
The timeout for new network connections to hosts in the cluster.
|
Cluster.Builder |
setConnectTimeout(com.google.protobuf.Duration value)
The timeout for new network connections to hosts in the cluster.
|
Cluster.Builder |
setDnsFailureRefreshRate(Cluster.RefreshRate.Builder builderForValue)
If the DNS failure refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this is used as the cluster’s DNS refresh rate when requests are failing.
|
Cluster.Builder |
setDnsFailureRefreshRate(Cluster.RefreshRate value)
If the DNS failure refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this is used as the cluster’s DNS refresh rate when requests are failing.
|
Cluster.Builder |
setDnsLookupFamily(Cluster.DnsLookupFamily value)
The DNS IP address resolution policy.
|
Cluster.Builder |
setDnsLookupFamilyValue(int value)
The DNS IP address resolution policy.
|
Cluster.Builder |
setDnsRefreshRate(com.google.protobuf.Duration.Builder builderForValue)
If the DNS refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used as the cluster’s DNS refresh
rate.
|
Cluster.Builder |
setDnsRefreshRate(com.google.protobuf.Duration value)
If the DNS refresh rate is specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used as the cluster’s DNS refresh
rate.
|
Cluster.Builder |
setDnsResolvers(int index,
Address.Builder builderForValue)
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
Cluster.Builder |
setDnsResolvers(int index,
Address value)
If DNS resolvers are specified and the cluster type is either
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`,
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`,
this value is used to specify the cluster’s dns resolvers.
|
Cluster.Builder |
setEdsClusterConfig(Cluster.EdsClusterConfig.Builder builderForValue)
Configuration to use for EDS updates for the Cluster.
|
Cluster.Builder |
setEdsClusterConfig(Cluster.EdsClusterConfig value)
Configuration to use for EDS updates for the Cluster.
|
Cluster.Builder |
setField(com.google.protobuf.Descriptors.FieldDescriptor field,
Object value) |
Cluster.Builder |
setFilters(int index,
Filter.Builder builderForValue)
An (optional) network filter chain, listed in the order the filters should be applied.
|
Cluster.Builder |
setFilters(int index,
Filter value)
An (optional) network filter chain, listed in the order the filters should be applied.
|
Cluster.Builder |
setHealthChecks(int index,
HealthCheck.Builder builderForValue)
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
Cluster.Builder |
setHealthChecks(int index,
HealthCheck value)
Optional :ref:`active health checking <arch_overview_health_checking>`
configuration for the cluster.
|
Cluster.Builder |
setIgnoreHealthOnHostRemoval(boolean value)
If set to true, Envoy will ignore the health value of a host when processing its removal
from service discovery.
|
Cluster.Builder |
setLbPolicy(Cluster.LbPolicy value)
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use
when picking a host in the cluster.
|
Cluster.Builder |
setLbPolicyValue(int value)
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use
when picking a host in the cluster.
|
Cluster.Builder |
setLbSubsetConfig(Cluster.LbSubsetConfig.Builder builderForValue)
Configuration for load balancing subsetting.
|
Cluster.Builder |
setLbSubsetConfig(Cluster.LbSubsetConfig value)
Configuration for load balancing subsetting.
|
Cluster.Builder |
setLeastRequestLbConfig(Cluster.LeastRequestLbConfig.Builder builderForValue)
Optional configuration for the LeastRequest load balancing policy.
|
Cluster.Builder |
setLeastRequestLbConfig(Cluster.LeastRequestLbConfig value)
Optional configuration for the LeastRequest load balancing policy.
|
Cluster.Builder |
setLoadAssignment(ClusterLoadAssignment.Builder builderForValue)
Setting this is required for specifying members of
:ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`,
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.
|
Cluster.Builder |
setLoadAssignment(ClusterLoadAssignment value)
Setting this is required for specifying members of
:ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`,
:ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`
or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.
|
Cluster.Builder |
setLoadBalancingPolicy(LoadBalancingPolicy.Builder builderForValue)
[#not-implemented-hide:] New mechanism for LB policy configuration.
|
Cluster.Builder |
setLoadBalancingPolicy(LoadBalancingPolicy value)
[#not-implemented-hide:] New mechanism for LB policy configuration.
|
Cluster.Builder |
setLrsServer(ConfigSource.Builder builderForValue)
[#not-implemented-hide:]
If present, tells the client where to send load reports via LRS.
|
Cluster.Builder |
setLrsServer(ConfigSource value)
[#not-implemented-hide:]
If present, tells the client where to send load reports via LRS.
|
Cluster.Builder |
setMaglevLbConfig(Cluster.MaglevLbConfig.Builder builderForValue)
Optional configuration for the Maglev load balancing policy.
|
Cluster.Builder |
setMaglevLbConfig(Cluster.MaglevLbConfig value)
Optional configuration for the Maglev load balancing policy.
|
Cluster.Builder |
setMaxRequestsPerConnection(com.google.protobuf.UInt32Value.Builder builderForValue)
Optional maximum requests for a single upstream connection.
|
Cluster.Builder |
setMaxRequestsPerConnection(com.google.protobuf.UInt32Value value)
Optional maximum requests for a single upstream connection.
|
Cluster.Builder |
setMetadata(Metadata.Builder builderForValue)
The Metadata field can be used to provide additional information about the
cluster.
|
Cluster.Builder |
setMetadata(Metadata value)
The Metadata field can be used to provide additional information about the
cluster.
|
Cluster.Builder |
setName(String value)
Supplies the name of the cluster which must be unique across all clusters.
|
Cluster.Builder |
setNameBytes(com.google.protobuf.ByteString value)
Supplies the name of the cluster which must be unique across all clusters.
|
Cluster.Builder |
setOriginalDstLbConfig(Cluster.OriginalDstLbConfig.Builder builderForValue)
Optional configuration for the Original Destination load balancing policy.
|
Cluster.Builder |
setOriginalDstLbConfig(Cluster.OriginalDstLbConfig value)
Optional configuration for the Original Destination load balancing policy.
|
Cluster.Builder |
setOutlierDetection(OutlierDetection.Builder builderForValue)
If specified, outlier detection will be enabled for this upstream cluster.
|
Cluster.Builder |
setOutlierDetection(OutlierDetection value)
If specified, outlier detection will be enabled for this upstream cluster.
|
Cluster.Builder |
setPerConnectionBufferLimitBytes(com.google.protobuf.UInt32Value.Builder builderForValue)
Soft limit on size of the cluster’s connections read and write buffers.
|
Cluster.Builder |
setPerConnectionBufferLimitBytes(com.google.protobuf.UInt32Value value)
Soft limit on size of the cluster’s connections read and write buffers.
|
Cluster.Builder |
setPreconnectPolicy(Cluster.PreconnectPolicy.Builder builderForValue)
[#not-implemented-hide:]
Preconnect configuration for this cluster.
|
Cluster.Builder |
setPreconnectPolicy(Cluster.PreconnectPolicy value)
[#not-implemented-hide:]
Preconnect configuration for this cluster.
|
Cluster.Builder |
setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field,
int index,
Object value) |
Cluster.Builder |
setRespectDnsTtl(boolean value)
Optional configuration for setting cluster's DNS refresh rate.
|
Cluster.Builder |
setRingHashLbConfig(Cluster.RingHashLbConfig.Builder builderForValue)
Optional configuration for the Ring Hash load balancing policy.
|
Cluster.Builder |
setRingHashLbConfig(Cluster.RingHashLbConfig value)
Optional configuration for the Ring Hash load balancing policy.
|
Cluster.Builder |
setTrackClusterStats(TrackClusterStats.Builder builderForValue)
Configuration to track optional cluster stats.
|
Cluster.Builder |
setTrackClusterStats(TrackClusterStats value)
Configuration to track optional cluster stats.
|
Cluster.Builder |
setTransportSocket(TransportSocket.Builder builderForValue)
Optional custom transport socket implementation to use for upstream connections.
|
Cluster.Builder |
setTransportSocket(TransportSocket value)
Optional custom transport socket implementation to use for upstream connections.
|
Cluster.Builder |
setTransportSocketMatches(int index,
Cluster.TransportSocketMatch.Builder builderForValue)
Configuration to use different transport sockets for different endpoints.
|
Cluster.Builder |
setTransportSocketMatches(int index,
Cluster.TransportSocketMatch value)
Configuration to use different transport sockets for different endpoints.
|
Cluster.Builder |
setType(Cluster.DiscoveryType value)
The :ref:`service discovery type <arch_overview_service_discovery_types>`
to use for resolving the cluster.
|
Cluster.Builder |
setTypeValue(int value)
The :ref:`service discovery type <arch_overview_service_discovery_types>`
to use for resolving the cluster.
|
Cluster.Builder |
setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) |
Cluster.Builder |
setUpstreamBindConfig(BindConfig.Builder builderForValue)
Optional configuration used to bind newly established upstream connections.
|
Cluster.Builder |
setUpstreamBindConfig(BindConfig value)
Optional configuration used to bind newly established upstream connections.
|
Cluster.Builder |
setUpstreamConfig(TypedExtensionConfig.Builder builderForValue)
Optional customization and configuration of upstream connection pool, and upstream type.
|
Cluster.Builder |
setUpstreamConfig(TypedExtensionConfig value)
Optional customization and configuration of upstream connection pool, and upstream type.
|
Cluster.Builder |
setUpstreamConnectionOptions(UpstreamConnectionOptions.Builder builderForValue)
Optional options for upstream connections.
|
Cluster.Builder |
setUpstreamConnectionOptions(UpstreamConnectionOptions value)
Optional options for upstream connections.
|
Cluster.Builder |
setUseTcpForDnsLookups(boolean value)
[#next-major-version: Reconcile DNS options in a single message.]
|
getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof, isClean, markClean, newBuilderForField, onBuilt, onChanged, setUnknownFieldsProto3findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toStringaddAll, addAll, mergeFrom, newUninitializedMessageExceptionequals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitpublic static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
protected com.google.protobuf.MapField internalGetMapField(int number)
internalGetMapField in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>protected com.google.protobuf.MapField internalGetMutableMapField(int number)
internalGetMutableMapField in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>public Cluster.Builder clear()
clear in interface com.google.protobuf.Message.Builderclear in interface com.google.protobuf.MessageLite.Builderclear in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
getDescriptorForType in interface com.google.protobuf.Message.BuildergetDescriptorForType in interface com.google.protobuf.MessageOrBuildergetDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>public Cluster getDefaultInstanceForType()
getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuildergetDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilderpublic Cluster build()
build in interface com.google.protobuf.Message.Builderbuild in interface com.google.protobuf.MessageLite.Builderpublic Cluster buildPartial()
buildPartial in interface com.google.protobuf.Message.BuilderbuildPartial in interface com.google.protobuf.MessageLite.Builderpublic Cluster.Builder clone()
clone in interface com.google.protobuf.Message.Builderclone in interface com.google.protobuf.MessageLite.Builderclone in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>public Cluster.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
setField in interface com.google.protobuf.Message.BuildersetField in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>public Cluster.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
clearField in interface com.google.protobuf.Message.BuilderclearField in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>public Cluster.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
clearOneof in interface com.google.protobuf.Message.BuilderclearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>public Cluster.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)
setRepeatedField in interface com.google.protobuf.Message.BuildersetRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>public Cluster.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
addRepeatedField in interface com.google.protobuf.Message.BuilderaddRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>public Cluster.Builder mergeFrom(com.google.protobuf.Message other)
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<Cluster.Builder>public Cluster.Builder mergeFrom(Cluster other)
public final boolean isInitialized()
isInitialized in interface com.google.protobuf.MessageLiteOrBuilderisInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>public Cluster.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in interface com.google.protobuf.MessageLite.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<Cluster.Builder>IOExceptionpublic Cluster.ClusterDiscoveryTypeCase getClusterDiscoveryTypeCase()
getClusterDiscoveryTypeCase in interface ClusterOrBuilderpublic Cluster.Builder clearClusterDiscoveryType()
public Cluster.LbConfigCase getLbConfigCase()
getLbConfigCase in interface ClusterOrBuilderpublic Cluster.Builder clearLbConfig()
public List<Cluster.TransportSocketMatch> getTransportSocketMatchesList()
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;getTransportSocketMatchesList in interface ClusterOrBuilderpublic int getTransportSocketMatchesCount()
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;getTransportSocketMatchesCount in interface ClusterOrBuilderpublic Cluster.TransportSocketMatch getTransportSocketMatches(int index)
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;getTransportSocketMatches in interface ClusterOrBuilderpublic Cluster.Builder setTransportSocketMatches(int index, Cluster.TransportSocketMatch value)
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;public Cluster.Builder setTransportSocketMatches(int index, Cluster.TransportSocketMatch.Builder builderForValue)
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;public Cluster.Builder addTransportSocketMatches(Cluster.TransportSocketMatch value)
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;public Cluster.Builder addTransportSocketMatches(int index, Cluster.TransportSocketMatch value)
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;public Cluster.Builder addTransportSocketMatches(Cluster.TransportSocketMatch.Builder builderForValue)
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;public Cluster.Builder addTransportSocketMatches(int index, Cluster.TransportSocketMatch.Builder builderForValue)
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;public Cluster.Builder addAllTransportSocketMatches(Iterable<? extends Cluster.TransportSocketMatch> values)
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;public Cluster.Builder clearTransportSocketMatches()
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;public Cluster.Builder removeTransportSocketMatches(int index)
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;public Cluster.TransportSocketMatch.Builder getTransportSocketMatchesBuilder(int index)
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;public Cluster.TransportSocketMatchOrBuilder getTransportSocketMatchesOrBuilder(int index)
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;getTransportSocketMatchesOrBuilder in interface ClusterOrBuilderpublic List<? extends Cluster.TransportSocketMatchOrBuilder> getTransportSocketMatchesOrBuilderList()
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;getTransportSocketMatchesOrBuilderList in interface ClusterOrBuilderpublic Cluster.TransportSocketMatch.Builder addTransportSocketMatchesBuilder()
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;public Cluster.TransportSocketMatch.Builder addTransportSocketMatchesBuilder(int index)
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;public List<Cluster.TransportSocketMatch.Builder> getTransportSocketMatchesBuilderList()
Configuration to use different transport sockets for different endpoints.
The entry of *envoy.transport_socket_match* in the
:ref:`LbEndpoint.Metadata <envoy_api_field_config.endpoint.v3.LbEndpoint.metadata>`
is used to match against the transport sockets as they appear in the list. The first
:ref:`match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` is used.
For example, with the following match
.. code-block:: yaml
transport_socket_matches:
- name: "enableMTLS"
match:
acceptMTLS: true
transport_socket:
name: envoy.transport_sockets.tls
config: { ... } # tls socket configuration
- name: "defaultToPlaintext"
match: {}
transport_socket:
name: envoy.transport_sockets.raw_buffer
Connections to the endpoints whose metadata value under *envoy.transport_socket_match*
having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.
If a :ref:`socket match <envoy_api_msg_config.cluster.v4alpha.Cluster.TransportSocketMatch>` with empty match
criteria is provided, that always match any endpoint. For example, the "defaultToPlaintext"
socket match in case above.
If an endpoint metadata's value under *envoy.transport_socket_match* does not match any
*TransportSocketMatch*, socket configuration fallbacks to use the *tls_context* or
*transport_socket* specified in this cluster.
This field allows gradual and flexible transport socket configuration changes.
The metadata of endpoints in EDS can indicate transport socket capabilities. For example,
an endpoint's metadata can have two key value pairs as "acceptMTLS": "true",
"acceptPlaintext": "true". While some other endpoints, only accepting plaintext traffic
has "acceptPlaintext": "true" metadata information.
Then the xDS server can configure the CDS to a client, Envoy A, to send mutual TLS
traffic for endpoints with "acceptMTLS": "true", by adding a corresponding
*TransportSocketMatch* in this field. Other client Envoys receive CDS without
*transport_socket_match* set, and still send plain text traffic to the same cluster.
This field can be used to specify custom transport socket configurations for health
checks by adding matching key/value pairs in a health check's
:ref:`transport socket match criteria <envoy_api_field_config.core.v4alpha.HealthCheck.transport_socket_match_criteria>` field.
[#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v4alpha.Cluster.TransportSocketMatch transport_socket_matches = 43;public String getName()
Supplies the name of the cluster which must be unique across all clusters. The cluster name is used when emitting :ref:`statistics <config_cluster_manager_cluster_stats>` if :ref:`alt_stat_name <envoy_api_field_config.cluster.v4alpha.Cluster.alt_stat_name>` is not provided. Any ``:`` in the cluster name will be converted to ``_`` when emitting statistics.
string name = 1 [(.validate.rules) = { ... }getName in interface ClusterOrBuilderpublic com.google.protobuf.ByteString getNameBytes()
Supplies the name of the cluster which must be unique across all clusters. The cluster name is used when emitting :ref:`statistics <config_cluster_manager_cluster_stats>` if :ref:`alt_stat_name <envoy_api_field_config.cluster.v4alpha.Cluster.alt_stat_name>` is not provided. Any ``:`` in the cluster name will be converted to ``_`` when emitting statistics.
string name = 1 [(.validate.rules) = { ... }getNameBytes in interface ClusterOrBuilderpublic Cluster.Builder setName(String value)
Supplies the name of the cluster which must be unique across all clusters. The cluster name is used when emitting :ref:`statistics <config_cluster_manager_cluster_stats>` if :ref:`alt_stat_name <envoy_api_field_config.cluster.v4alpha.Cluster.alt_stat_name>` is not provided. Any ``:`` in the cluster name will be converted to ``_`` when emitting statistics.
string name = 1 [(.validate.rules) = { ... }public Cluster.Builder clearName()
Supplies the name of the cluster which must be unique across all clusters. The cluster name is used when emitting :ref:`statistics <config_cluster_manager_cluster_stats>` if :ref:`alt_stat_name <envoy_api_field_config.cluster.v4alpha.Cluster.alt_stat_name>` is not provided. Any ``:`` in the cluster name will be converted to ``_`` when emitting statistics.
string name = 1 [(.validate.rules) = { ... }public Cluster.Builder setNameBytes(com.google.protobuf.ByteString value)
Supplies the name of the cluster which must be unique across all clusters. The cluster name is used when emitting :ref:`statistics <config_cluster_manager_cluster_stats>` if :ref:`alt_stat_name <envoy_api_field_config.cluster.v4alpha.Cluster.alt_stat_name>` is not provided. Any ``:`` in the cluster name will be converted to ``_`` when emitting statistics.
string name = 1 [(.validate.rules) = { ... }public String getAltStatName()
An optional alternative to the cluster name to be used while emitting stats. Any ``:`` in the name will be converted to ``_`` when emitting statistics. This should not be confused with :ref:`Router Filter Header <config_http_filters_router_x-envoy-upstream-alt-stat-name>`.
string alt_stat_name = 28;getAltStatName in interface ClusterOrBuilderpublic com.google.protobuf.ByteString getAltStatNameBytes()
An optional alternative to the cluster name to be used while emitting stats. Any ``:`` in the name will be converted to ``_`` when emitting statistics. This should not be confused with :ref:`Router Filter Header <config_http_filters_router_x-envoy-upstream-alt-stat-name>`.
string alt_stat_name = 28;getAltStatNameBytes in interface ClusterOrBuilderpublic Cluster.Builder setAltStatName(String value)
An optional alternative to the cluster name to be used while emitting stats. Any ``:`` in the name will be converted to ``_`` when emitting statistics. This should not be confused with :ref:`Router Filter Header <config_http_filters_router_x-envoy-upstream-alt-stat-name>`.
string alt_stat_name = 28;public Cluster.Builder clearAltStatName()
An optional alternative to the cluster name to be used while emitting stats. Any ``:`` in the name will be converted to ``_`` when emitting statistics. This should not be confused with :ref:`Router Filter Header <config_http_filters_router_x-envoy-upstream-alt-stat-name>`.
string alt_stat_name = 28;public Cluster.Builder setAltStatNameBytes(com.google.protobuf.ByteString value)
An optional alternative to the cluster name to be used while emitting stats. Any ``:`` in the name will be converted to ``_`` when emitting statistics. This should not be confused with :ref:`Router Filter Header <config_http_filters_router_x-envoy-upstream-alt-stat-name>`.
string alt_stat_name = 28;public int getTypeValue()
The :ref:`service discovery type <arch_overview_service_discovery_types>` to use for resolving the cluster.
.envoy.config.cluster.v4alpha.Cluster.DiscoveryType type = 2 [(.validate.rules) = { ... }getTypeValue in interface ClusterOrBuilderpublic Cluster.Builder setTypeValue(int value)
The :ref:`service discovery type <arch_overview_service_discovery_types>` to use for resolving the cluster.
.envoy.config.cluster.v4alpha.Cluster.DiscoveryType type = 2 [(.validate.rules) = { ... }public Cluster.DiscoveryType getType()
The :ref:`service discovery type <arch_overview_service_discovery_types>` to use for resolving the cluster.
.envoy.config.cluster.v4alpha.Cluster.DiscoveryType type = 2 [(.validate.rules) = { ... }getType in interface ClusterOrBuilderpublic Cluster.Builder setType(Cluster.DiscoveryType value)
The :ref:`service discovery type <arch_overview_service_discovery_types>` to use for resolving the cluster.
.envoy.config.cluster.v4alpha.Cluster.DiscoveryType type = 2 [(.validate.rules) = { ... }public Cluster.Builder clearType()
The :ref:`service discovery type <arch_overview_service_discovery_types>` to use for resolving the cluster.
.envoy.config.cluster.v4alpha.Cluster.DiscoveryType type = 2 [(.validate.rules) = { ... }public boolean hasClusterType()
The custom cluster type.
.envoy.config.cluster.v4alpha.Cluster.CustomClusterType cluster_type = 38;hasClusterType in interface ClusterOrBuilderpublic Cluster.CustomClusterType getClusterType()
The custom cluster type.
.envoy.config.cluster.v4alpha.Cluster.CustomClusterType cluster_type = 38;getClusterType in interface ClusterOrBuilderpublic Cluster.Builder setClusterType(Cluster.CustomClusterType value)
The custom cluster type.
.envoy.config.cluster.v4alpha.Cluster.CustomClusterType cluster_type = 38;public Cluster.Builder setClusterType(Cluster.CustomClusterType.Builder builderForValue)
The custom cluster type.
.envoy.config.cluster.v4alpha.Cluster.CustomClusterType cluster_type = 38;public Cluster.Builder mergeClusterType(Cluster.CustomClusterType value)
The custom cluster type.
.envoy.config.cluster.v4alpha.Cluster.CustomClusterType cluster_type = 38;public Cluster.Builder clearClusterType()
The custom cluster type.
.envoy.config.cluster.v4alpha.Cluster.CustomClusterType cluster_type = 38;public Cluster.CustomClusterType.Builder getClusterTypeBuilder()
The custom cluster type.
.envoy.config.cluster.v4alpha.Cluster.CustomClusterType cluster_type = 38;public Cluster.CustomClusterTypeOrBuilder getClusterTypeOrBuilder()
The custom cluster type.
.envoy.config.cluster.v4alpha.Cluster.CustomClusterType cluster_type = 38;getClusterTypeOrBuilder in interface ClusterOrBuilderpublic boolean hasEdsClusterConfig()
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v4alpha.Cluster.EdsClusterConfig eds_cluster_config = 3;hasEdsClusterConfig in interface ClusterOrBuilderpublic Cluster.EdsClusterConfig getEdsClusterConfig()
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v4alpha.Cluster.EdsClusterConfig eds_cluster_config = 3;getEdsClusterConfig in interface ClusterOrBuilderpublic Cluster.Builder setEdsClusterConfig(Cluster.EdsClusterConfig value)
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v4alpha.Cluster.EdsClusterConfig eds_cluster_config = 3;public Cluster.Builder setEdsClusterConfig(Cluster.EdsClusterConfig.Builder builderForValue)
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v4alpha.Cluster.EdsClusterConfig eds_cluster_config = 3;public Cluster.Builder mergeEdsClusterConfig(Cluster.EdsClusterConfig value)
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v4alpha.Cluster.EdsClusterConfig eds_cluster_config = 3;public Cluster.Builder clearEdsClusterConfig()
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v4alpha.Cluster.EdsClusterConfig eds_cluster_config = 3;public Cluster.EdsClusterConfig.Builder getEdsClusterConfigBuilder()
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v4alpha.Cluster.EdsClusterConfig eds_cluster_config = 3;public Cluster.EdsClusterConfigOrBuilder getEdsClusterConfigOrBuilder()
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v4alpha.Cluster.EdsClusterConfig eds_cluster_config = 3;getEdsClusterConfigOrBuilder in interface ClusterOrBuilderpublic boolean hasConnectTimeout()
The timeout for new network connections to hosts in the cluster.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }hasConnectTimeout in interface ClusterOrBuilderpublic com.google.protobuf.Duration getConnectTimeout()
The timeout for new network connections to hosts in the cluster.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }getConnectTimeout in interface ClusterOrBuilderpublic Cluster.Builder setConnectTimeout(com.google.protobuf.Duration value)
The timeout for new network connections to hosts in the cluster.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }public Cluster.Builder setConnectTimeout(com.google.protobuf.Duration.Builder builderForValue)
The timeout for new network connections to hosts in the cluster.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }public Cluster.Builder mergeConnectTimeout(com.google.protobuf.Duration value)
The timeout for new network connections to hosts in the cluster.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }public Cluster.Builder clearConnectTimeout()
The timeout for new network connections to hosts in the cluster.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }public com.google.protobuf.Duration.Builder getConnectTimeoutBuilder()
The timeout for new network connections to hosts in the cluster.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }public com.google.protobuf.DurationOrBuilder getConnectTimeoutOrBuilder()
The timeout for new network connections to hosts in the cluster.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }getConnectTimeoutOrBuilder in interface ClusterOrBuilderpublic boolean hasPerConnectionBufferLimitBytes()
Soft limit on size of the cluster’s connections read and write buffers. If unspecified, an implementation defined default is applied (1MiB).
.google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }hasPerConnectionBufferLimitBytes in interface ClusterOrBuilderpublic com.google.protobuf.UInt32Value getPerConnectionBufferLimitBytes()
Soft limit on size of the cluster’s connections read and write buffers. If unspecified, an implementation defined default is applied (1MiB).
.google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }getPerConnectionBufferLimitBytes in interface ClusterOrBuilderpublic Cluster.Builder setPerConnectionBufferLimitBytes(com.google.protobuf.UInt32Value value)
Soft limit on size of the cluster’s connections read and write buffers. If unspecified, an implementation defined default is applied (1MiB).
.google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }public Cluster.Builder setPerConnectionBufferLimitBytes(com.google.protobuf.UInt32Value.Builder builderForValue)
Soft limit on size of the cluster’s connections read and write buffers. If unspecified, an implementation defined default is applied (1MiB).
.google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }public Cluster.Builder mergePerConnectionBufferLimitBytes(com.google.protobuf.UInt32Value value)
Soft limit on size of the cluster’s connections read and write buffers. If unspecified, an implementation defined default is applied (1MiB).
.google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }public Cluster.Builder clearPerConnectionBufferLimitBytes()
Soft limit on size of the cluster’s connections read and write buffers. If unspecified, an implementation defined default is applied (1MiB).
.google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }public com.google.protobuf.UInt32Value.Builder getPerConnectionBufferLimitBytesBuilder()
Soft limit on size of the cluster’s connections read and write buffers. If unspecified, an implementation defined default is applied (1MiB).
.google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }public com.google.protobuf.UInt32ValueOrBuilder getPerConnectionBufferLimitBytesOrBuilder()
Soft limit on size of the cluster’s connections read and write buffers. If unspecified, an implementation defined default is applied (1MiB).
.google.protobuf.UInt32Value per_connection_buffer_limit_bytes = 5 [(.udpa.annotations.security) = { ... }getPerConnectionBufferLimitBytesOrBuilder in interface ClusterOrBuilderpublic int getLbPolicyValue()
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use when picking a host in the cluster. [#comment:TODO: Remove enum constraint :ref:`LOAD_BALANCING_POLICY_CONFIG<envoy_api_enum_value_config.cluster.v4alpha.Cluster.LbPolicy.LOAD_BALANCING_POLICY_CONFIG>` when implemented.]
.envoy.config.cluster.v4alpha.Cluster.LbPolicy lb_policy = 6 [(.validate.rules) = { ... }getLbPolicyValue in interface ClusterOrBuilderpublic Cluster.Builder setLbPolicyValue(int value)
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use when picking a host in the cluster. [#comment:TODO: Remove enum constraint :ref:`LOAD_BALANCING_POLICY_CONFIG<envoy_api_enum_value_config.cluster.v4alpha.Cluster.LbPolicy.LOAD_BALANCING_POLICY_CONFIG>` when implemented.]
.envoy.config.cluster.v4alpha.Cluster.LbPolicy lb_policy = 6 [(.validate.rules) = { ... }public Cluster.LbPolicy getLbPolicy()
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use when picking a host in the cluster. [#comment:TODO: Remove enum constraint :ref:`LOAD_BALANCING_POLICY_CONFIG<envoy_api_enum_value_config.cluster.v4alpha.Cluster.LbPolicy.LOAD_BALANCING_POLICY_CONFIG>` when implemented.]
.envoy.config.cluster.v4alpha.Cluster.LbPolicy lb_policy = 6 [(.validate.rules) = { ... }getLbPolicy in interface ClusterOrBuilderpublic Cluster.Builder setLbPolicy(Cluster.LbPolicy value)
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use when picking a host in the cluster. [#comment:TODO: Remove enum constraint :ref:`LOAD_BALANCING_POLICY_CONFIG<envoy_api_enum_value_config.cluster.v4alpha.Cluster.LbPolicy.LOAD_BALANCING_POLICY_CONFIG>` when implemented.]
.envoy.config.cluster.v4alpha.Cluster.LbPolicy lb_policy = 6 [(.validate.rules) = { ... }public Cluster.Builder clearLbPolicy()
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use when picking a host in the cluster. [#comment:TODO: Remove enum constraint :ref:`LOAD_BALANCING_POLICY_CONFIG<envoy_api_enum_value_config.cluster.v4alpha.Cluster.LbPolicy.LOAD_BALANCING_POLICY_CONFIG>` when implemented.]
.envoy.config.cluster.v4alpha.Cluster.LbPolicy lb_policy = 6 [(.validate.rules) = { ... }public boolean hasLoadAssignment()
Setting this is required for specifying members of :ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters. This field supersedes the *hosts* field in the v2 API. .. attention:: Setting this allows non-EDS cluster types to contain embedded EDS equivalent :ref:`endpoint assignments<envoy_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;hasLoadAssignment in interface ClusterOrBuilderpublic ClusterLoadAssignment getLoadAssignment()
Setting this is required for specifying members of :ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters. This field supersedes the *hosts* field in the v2 API. .. attention:: Setting this allows non-EDS cluster types to contain embedded EDS equivalent :ref:`endpoint assignments<envoy_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;getLoadAssignment in interface ClusterOrBuilderpublic Cluster.Builder setLoadAssignment(ClusterLoadAssignment value)
Setting this is required for specifying members of :ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters. This field supersedes the *hosts* field in the v2 API. .. attention:: Setting this allows non-EDS cluster types to contain embedded EDS equivalent :ref:`endpoint assignments<envoy_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;public Cluster.Builder setLoadAssignment(ClusterLoadAssignment.Builder builderForValue)
Setting this is required for specifying members of :ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters. This field supersedes the *hosts* field in the v2 API. .. attention:: Setting this allows non-EDS cluster types to contain embedded EDS equivalent :ref:`endpoint assignments<envoy_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;public Cluster.Builder mergeLoadAssignment(ClusterLoadAssignment value)
Setting this is required for specifying members of :ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters. This field supersedes the *hosts* field in the v2 API. .. attention:: Setting this allows non-EDS cluster types to contain embedded EDS equivalent :ref:`endpoint assignments<envoy_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;public Cluster.Builder clearLoadAssignment()
Setting this is required for specifying members of :ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters. This field supersedes the *hosts* field in the v2 API. .. attention:: Setting this allows non-EDS cluster types to contain embedded EDS equivalent :ref:`endpoint assignments<envoy_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;public ClusterLoadAssignment.Builder getLoadAssignmentBuilder()
Setting this is required for specifying members of :ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters. This field supersedes the *hosts* field in the v2 API. .. attention:: Setting this allows non-EDS cluster types to contain embedded EDS equivalent :ref:`endpoint assignments<envoy_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;public ClusterLoadAssignmentOrBuilder getLoadAssignmentOrBuilder()
Setting this is required for specifying members of :ref:`STATIC<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` clusters. This field supersedes the *hosts* field in the v2 API. .. attention:: Setting this allows non-EDS cluster types to contain embedded EDS equivalent :ref:`endpoint assignments<envoy_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;getLoadAssignmentOrBuilder in interface ClusterOrBuilderpublic List<HealthCheck> getHealthChecksList()
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;getHealthChecksList in interface ClusterOrBuilderpublic int getHealthChecksCount()
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;getHealthChecksCount in interface ClusterOrBuilderpublic HealthCheck getHealthChecks(int index)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;getHealthChecks in interface ClusterOrBuilderpublic Cluster.Builder setHealthChecks(int index, HealthCheck value)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;public Cluster.Builder setHealthChecks(int index, HealthCheck.Builder builderForValue)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;public Cluster.Builder addHealthChecks(HealthCheck value)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;public Cluster.Builder addHealthChecks(int index, HealthCheck value)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;public Cluster.Builder addHealthChecks(HealthCheck.Builder builderForValue)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;public Cluster.Builder addHealthChecks(int index, HealthCheck.Builder builderForValue)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;public Cluster.Builder addAllHealthChecks(Iterable<? extends HealthCheck> values)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;public Cluster.Builder clearHealthChecks()
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;public Cluster.Builder removeHealthChecks(int index)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;public HealthCheck.Builder getHealthChecksBuilder(int index)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;public HealthCheckOrBuilder getHealthChecksOrBuilder(int index)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;getHealthChecksOrBuilder in interface ClusterOrBuilderpublic List<? extends HealthCheckOrBuilder> getHealthChecksOrBuilderList()
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;getHealthChecksOrBuilderList in interface ClusterOrBuilderpublic HealthCheck.Builder addHealthChecksBuilder()
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;public HealthCheck.Builder addHealthChecksBuilder(int index)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;public List<HealthCheck.Builder> getHealthChecksBuilderList()
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster. If no configuration is specified no health checking will be done and all cluster members will be considered healthy at all times.
repeated .envoy.config.core.v4alpha.HealthCheck health_checks = 8;public boolean hasMaxRequestsPerConnection()
Optional maximum requests for a single upstream connection. This parameter is respected by both the HTTP/1.1 and HTTP/2 connection pool implementations. If not specified, there is no limit. Setting this parameter to 1 will effectively disable keep alive.
.google.protobuf.UInt32Value max_requests_per_connection = 9;hasMaxRequestsPerConnection in interface ClusterOrBuilderpublic com.google.protobuf.UInt32Value getMaxRequestsPerConnection()
Optional maximum requests for a single upstream connection. This parameter is respected by both the HTTP/1.1 and HTTP/2 connection pool implementations. If not specified, there is no limit. Setting this parameter to 1 will effectively disable keep alive.
.google.protobuf.UInt32Value max_requests_per_connection = 9;getMaxRequestsPerConnection in interface ClusterOrBuilderpublic Cluster.Builder setMaxRequestsPerConnection(com.google.protobuf.UInt32Value value)
Optional maximum requests for a single upstream connection. This parameter is respected by both the HTTP/1.1 and HTTP/2 connection pool implementations. If not specified, there is no limit. Setting this parameter to 1 will effectively disable keep alive.
.google.protobuf.UInt32Value max_requests_per_connection = 9;public Cluster.Builder setMaxRequestsPerConnection(com.google.protobuf.UInt32Value.Builder builderForValue)
Optional maximum requests for a single upstream connection. This parameter is respected by both the HTTP/1.1 and HTTP/2 connection pool implementations. If not specified, there is no limit. Setting this parameter to 1 will effectively disable keep alive.
.google.protobuf.UInt32Value max_requests_per_connection = 9;public Cluster.Builder mergeMaxRequestsPerConnection(com.google.protobuf.UInt32Value value)
Optional maximum requests for a single upstream connection. This parameter is respected by both the HTTP/1.1 and HTTP/2 connection pool implementations. If not specified, there is no limit. Setting this parameter to 1 will effectively disable keep alive.
.google.protobuf.UInt32Value max_requests_per_connection = 9;public Cluster.Builder clearMaxRequestsPerConnection()
Optional maximum requests for a single upstream connection. This parameter is respected by both the HTTP/1.1 and HTTP/2 connection pool implementations. If not specified, there is no limit. Setting this parameter to 1 will effectively disable keep alive.
.google.protobuf.UInt32Value max_requests_per_connection = 9;public com.google.protobuf.UInt32Value.Builder getMaxRequestsPerConnectionBuilder()
Optional maximum requests for a single upstream connection. This parameter is respected by both the HTTP/1.1 and HTTP/2 connection pool implementations. If not specified, there is no limit. Setting this parameter to 1 will effectively disable keep alive.
.google.protobuf.UInt32Value max_requests_per_connection = 9;public com.google.protobuf.UInt32ValueOrBuilder getMaxRequestsPerConnectionOrBuilder()
Optional maximum requests for a single upstream connection. This parameter is respected by both the HTTP/1.1 and HTTP/2 connection pool implementations. If not specified, there is no limit. Setting this parameter to 1 will effectively disable keep alive.
.google.protobuf.UInt32Value max_requests_per_connection = 9;getMaxRequestsPerConnectionOrBuilder in interface ClusterOrBuilderpublic boolean hasCircuitBreakers()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v4alpha.CircuitBreakers circuit_breakers = 10;hasCircuitBreakers in interface ClusterOrBuilderpublic CircuitBreakers getCircuitBreakers()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v4alpha.CircuitBreakers circuit_breakers = 10;getCircuitBreakers in interface ClusterOrBuilderpublic Cluster.Builder setCircuitBreakers(CircuitBreakers value)
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v4alpha.CircuitBreakers circuit_breakers = 10;public Cluster.Builder setCircuitBreakers(CircuitBreakers.Builder builderForValue)
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v4alpha.CircuitBreakers circuit_breakers = 10;public Cluster.Builder mergeCircuitBreakers(CircuitBreakers value)
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v4alpha.CircuitBreakers circuit_breakers = 10;public Cluster.Builder clearCircuitBreakers()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v4alpha.CircuitBreakers circuit_breakers = 10;public CircuitBreakers.Builder getCircuitBreakersBuilder()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v4alpha.CircuitBreakers circuit_breakers = 10;public CircuitBreakersOrBuilder getCircuitBreakersOrBuilder()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v4alpha.CircuitBreakers circuit_breakers = 10;getCircuitBreakersOrBuilder in interface ClusterOrBuilderpublic int getTypedExtensionProtocolOptionsCount()
ClusterOrBuilderThe extension_protocol_options field is used to provide extension-specific protocol options for upstream connections. The key should match the extension filter name, such as "envoy.filters.network.thrift_proxy". See the extension's documentation for details on specific options. [#next-major-version: make this a list of typed extensions.]
map<string, .google.protobuf.Any> typed_extension_protocol_options = 36;getTypedExtensionProtocolOptionsCount in interface ClusterOrBuilderpublic boolean containsTypedExtensionProtocolOptions(String key)
The extension_protocol_options field is used to provide extension-specific protocol options for upstream connections. The key should match the extension filter name, such as "envoy.filters.network.thrift_proxy". See the extension's documentation for details on specific options. [#next-major-version: make this a list of typed extensions.]
map<string, .google.protobuf.Any> typed_extension_protocol_options = 36;containsTypedExtensionProtocolOptions in interface ClusterOrBuilder@Deprecated public Map<String,com.google.protobuf.Any> getTypedExtensionProtocolOptions()
getTypedExtensionProtocolOptionsMap() instead.getTypedExtensionProtocolOptions in interface ClusterOrBuilderpublic Map<String,com.google.protobuf.Any> getTypedExtensionProtocolOptionsMap()
The extension_protocol_options field is used to provide extension-specific protocol options for upstream connections. The key should match the extension filter name, such as "envoy.filters.network.thrift_proxy". See the extension's documentation for details on specific options. [#next-major-version: make this a list of typed extensions.]
map<string, .google.protobuf.Any> typed_extension_protocol_options = 36;getTypedExtensionProtocolOptionsMap in interface ClusterOrBuilderpublic com.google.protobuf.Any getTypedExtensionProtocolOptionsOrDefault(String key, com.google.protobuf.Any defaultValue)
The extension_protocol_options field is used to provide extension-specific protocol options for upstream connections. The key should match the extension filter name, such as "envoy.filters.network.thrift_proxy". See the extension's documentation for details on specific options. [#next-major-version: make this a list of typed extensions.]
map<string, .google.protobuf.Any> typed_extension_protocol_options = 36;getTypedExtensionProtocolOptionsOrDefault in interface ClusterOrBuilderpublic com.google.protobuf.Any getTypedExtensionProtocolOptionsOrThrow(String key)
The extension_protocol_options field is used to provide extension-specific protocol options for upstream connections. The key should match the extension filter name, such as "envoy.filters.network.thrift_proxy". See the extension's documentation for details on specific options. [#next-major-version: make this a list of typed extensions.]
map<string, .google.protobuf.Any> typed_extension_protocol_options = 36;getTypedExtensionProtocolOptionsOrThrow in interface ClusterOrBuilderpublic Cluster.Builder clearTypedExtensionProtocolOptions()
public Cluster.Builder removeTypedExtensionProtocolOptions(String key)
The extension_protocol_options field is used to provide extension-specific protocol options for upstream connections. The key should match the extension filter name, such as "envoy.filters.network.thrift_proxy". See the extension's documentation for details on specific options. [#next-major-version: make this a list of typed extensions.]
map<string, .google.protobuf.Any> typed_extension_protocol_options = 36;@Deprecated public Map<String,com.google.protobuf.Any> getMutableTypedExtensionProtocolOptions()
public Cluster.Builder putTypedExtensionProtocolOptions(String key, com.google.protobuf.Any value)
The extension_protocol_options field is used to provide extension-specific protocol options for upstream connections. The key should match the extension filter name, such as "envoy.filters.network.thrift_proxy". See the extension's documentation for details on specific options. [#next-major-version: make this a list of typed extensions.]
map<string, .google.protobuf.Any> typed_extension_protocol_options = 36;public Cluster.Builder putAllTypedExtensionProtocolOptions(Map<String,com.google.protobuf.Any> values)
The extension_protocol_options field is used to provide extension-specific protocol options for upstream connections. The key should match the extension filter name, such as "envoy.filters.network.thrift_proxy". See the extension's documentation for details on specific options. [#next-major-version: make this a list of typed extensions.]
map<string, .google.protobuf.Any> typed_extension_protocol_options = 36;public boolean hasDnsRefreshRate()
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate. The value configured must be at least 1ms. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }hasDnsRefreshRate in interface ClusterOrBuilderpublic com.google.protobuf.Duration getDnsRefreshRate()
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate. The value configured must be at least 1ms. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }getDnsRefreshRate in interface ClusterOrBuilderpublic Cluster.Builder setDnsRefreshRate(com.google.protobuf.Duration value)
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate. The value configured must be at least 1ms. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }public Cluster.Builder setDnsRefreshRate(com.google.protobuf.Duration.Builder builderForValue)
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate. The value configured must be at least 1ms. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }public Cluster.Builder mergeDnsRefreshRate(com.google.protobuf.Duration value)
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate. The value configured must be at least 1ms. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }public Cluster.Builder clearDnsRefreshRate()
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate. The value configured must be at least 1ms. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }public com.google.protobuf.Duration.Builder getDnsRefreshRateBuilder()
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate. The value configured must be at least 1ms. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }public com.google.protobuf.DurationOrBuilder getDnsRefreshRateOrBuilder()
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate. The value configured must be at least 1ms. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }getDnsRefreshRateOrBuilder in interface ClusterOrBuilderpublic boolean hasDnsFailureRefreshRate()
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this is used as the cluster’s DNS refresh rate when requests are failing. If this setting is not specified, the failure refresh rate defaults to the DNS refresh rate. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v4alpha.Cluster.RefreshRate dns_failure_refresh_rate = 44;hasDnsFailureRefreshRate in interface ClusterOrBuilderpublic Cluster.RefreshRate getDnsFailureRefreshRate()
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this is used as the cluster’s DNS refresh rate when requests are failing. If this setting is not specified, the failure refresh rate defaults to the DNS refresh rate. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v4alpha.Cluster.RefreshRate dns_failure_refresh_rate = 44;getDnsFailureRefreshRate in interface ClusterOrBuilderpublic Cluster.Builder setDnsFailureRefreshRate(Cluster.RefreshRate value)
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this is used as the cluster’s DNS refresh rate when requests are failing. If this setting is not specified, the failure refresh rate defaults to the DNS refresh rate. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v4alpha.Cluster.RefreshRate dns_failure_refresh_rate = 44;public Cluster.Builder setDnsFailureRefreshRate(Cluster.RefreshRate.Builder builderForValue)
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this is used as the cluster’s DNS refresh rate when requests are failing. If this setting is not specified, the failure refresh rate defaults to the DNS refresh rate. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v4alpha.Cluster.RefreshRate dns_failure_refresh_rate = 44;public Cluster.Builder mergeDnsFailureRefreshRate(Cluster.RefreshRate value)
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this is used as the cluster’s DNS refresh rate when requests are failing. If this setting is not specified, the failure refresh rate defaults to the DNS refresh rate. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v4alpha.Cluster.RefreshRate dns_failure_refresh_rate = 44;public Cluster.Builder clearDnsFailureRefreshRate()
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this is used as the cluster’s DNS refresh rate when requests are failing. If this setting is not specified, the failure refresh rate defaults to the DNS refresh rate. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v4alpha.Cluster.RefreshRate dns_failure_refresh_rate = 44;public Cluster.RefreshRate.Builder getDnsFailureRefreshRateBuilder()
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this is used as the cluster’s DNS refresh rate when requests are failing. If this setting is not specified, the failure refresh rate defaults to the DNS refresh rate. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v4alpha.Cluster.RefreshRate dns_failure_refresh_rate = 44;public Cluster.RefreshRateOrBuilder getDnsFailureRefreshRateOrBuilder()
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this is used as the cluster’s DNS refresh rate when requests are failing. If this setting is not specified, the failure refresh rate defaults to the DNS refresh rate. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v4alpha.Cluster.RefreshRate dns_failure_refresh_rate = 44;getDnsFailureRefreshRateOrBuilder in interface ClusterOrBuilderpublic boolean getRespectDnsTtl()
Optional configuration for setting cluster's DNS refresh rate. If the value is set to true, cluster's DNS refresh rate will be set to resource record's TTL which comes from DNS resolution.
bool respect_dns_ttl = 39;getRespectDnsTtl in interface ClusterOrBuilderpublic Cluster.Builder setRespectDnsTtl(boolean value)
Optional configuration for setting cluster's DNS refresh rate. If the value is set to true, cluster's DNS refresh rate will be set to resource record's TTL which comes from DNS resolution.
bool respect_dns_ttl = 39;public Cluster.Builder clearRespectDnsTtl()
Optional configuration for setting cluster's DNS refresh rate. If the value is set to true, cluster's DNS refresh rate will be set to resource record's TTL which comes from DNS resolution.
bool respect_dns_ttl = 39;public int getDnsLookupFamilyValue()
The DNS IP address resolution policy. If this setting is not specified, the value defaults to :ref:`AUTO<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DnsLookupFamily.AUTO>`.
.envoy.config.cluster.v4alpha.Cluster.DnsLookupFamily dns_lookup_family = 17 [(.validate.rules) = { ... }getDnsLookupFamilyValue in interface ClusterOrBuilderpublic Cluster.Builder setDnsLookupFamilyValue(int value)
The DNS IP address resolution policy. If this setting is not specified, the value defaults to :ref:`AUTO<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DnsLookupFamily.AUTO>`.
.envoy.config.cluster.v4alpha.Cluster.DnsLookupFamily dns_lookup_family = 17 [(.validate.rules) = { ... }public Cluster.DnsLookupFamily getDnsLookupFamily()
The DNS IP address resolution policy. If this setting is not specified, the value defaults to :ref:`AUTO<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DnsLookupFamily.AUTO>`.
.envoy.config.cluster.v4alpha.Cluster.DnsLookupFamily dns_lookup_family = 17 [(.validate.rules) = { ... }getDnsLookupFamily in interface ClusterOrBuilderpublic Cluster.Builder setDnsLookupFamily(Cluster.DnsLookupFamily value)
The DNS IP address resolution policy. If this setting is not specified, the value defaults to :ref:`AUTO<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DnsLookupFamily.AUTO>`.
.envoy.config.cluster.v4alpha.Cluster.DnsLookupFamily dns_lookup_family = 17 [(.validate.rules) = { ... }public Cluster.Builder clearDnsLookupFamily()
The DNS IP address resolution policy. If this setting is not specified, the value defaults to :ref:`AUTO<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DnsLookupFamily.AUTO>`.
.envoy.config.cluster.v4alpha.Cluster.DnsLookupFamily dns_lookup_family = 17 [(.validate.rules) = { ... }public List<Address> getDnsResolversList()
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;getDnsResolversList in interface ClusterOrBuilderpublic int getDnsResolversCount()
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;getDnsResolversCount in interface ClusterOrBuilderpublic Address getDnsResolvers(int index)
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;getDnsResolvers in interface ClusterOrBuilderpublic Cluster.Builder setDnsResolvers(int index, Address value)
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;public Cluster.Builder setDnsResolvers(int index, Address.Builder builderForValue)
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;public Cluster.Builder addDnsResolvers(Address value)
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;public Cluster.Builder addDnsResolvers(int index, Address value)
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;public Cluster.Builder addDnsResolvers(Address.Builder builderForValue)
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;public Cluster.Builder addDnsResolvers(int index, Address.Builder builderForValue)
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;public Cluster.Builder addAllDnsResolvers(Iterable<? extends Address> values)
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;public Cluster.Builder clearDnsResolvers()
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;public Cluster.Builder removeDnsResolvers(int index)
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;public Address.Builder getDnsResolversBuilder(int index)
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;public AddressOrBuilder getDnsResolversOrBuilder(int index)
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;getDnsResolversOrBuilder in interface ClusterOrBuilderpublic List<? extends AddressOrBuilder> getDnsResolversOrBuilderList()
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;getDnsResolversOrBuilderList in interface ClusterOrBuilderpublic Address.Builder addDnsResolversBuilder()
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;public Address.Builder addDnsResolversBuilder(int index)
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;public List<Address.Builder> getDnsResolversBuilderList()
If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used to specify the cluster’s dns resolvers. If this setting is not specified, the value defaults to the default resolver, which uses /etc/resolv.conf for configuration. For cluster types other than :ref:`STRICT_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple's API only allows overriding DNS resolvers via system settings.
repeated .envoy.config.core.v4alpha.Address dns_resolvers = 18;public boolean getUseTcpForDnsLookups()
[#next-major-version: Reconcile DNS options in a single message.] Always use TCP queries instead of UDP queries for DNS lookups. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple' API only uses UDP for DNS resolution.
bool use_tcp_for_dns_lookups = 45;getUseTcpForDnsLookups in interface ClusterOrBuilderpublic Cluster.Builder setUseTcpForDnsLookups(boolean value)
[#next-major-version: Reconcile DNS options in a single message.] Always use TCP queries instead of UDP queries for DNS lookups. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple' API only uses UDP for DNS resolution.
bool use_tcp_for_dns_lookups = 45;public Cluster.Builder clearUseTcpForDnsLookups()
[#next-major-version: Reconcile DNS options in a single message.] Always use TCP queries instead of UDP queries for DNS lookups. Setting this value causes failure if the ``envoy.restart_features.use_apple_api_for_dns_lookups`` runtime value is true during server startup. Apple' API only uses UDP for DNS resolution.
bool use_tcp_for_dns_lookups = 45;public boolean hasOutlierDetection()
If specified, outlier detection will be enabled for this upstream cluster. Each of the configuration values can be overridden via :ref:`runtime values <config_cluster_manager_cluster_runtime_outlier_detection>`.
.envoy.config.cluster.v4alpha.OutlierDetection outlier_detection = 19;hasOutlierDetection in interface ClusterOrBuilderpublic OutlierDetection getOutlierDetection()
If specified, outlier detection will be enabled for this upstream cluster. Each of the configuration values can be overridden via :ref:`runtime values <config_cluster_manager_cluster_runtime_outlier_detection>`.
.envoy.config.cluster.v4alpha.OutlierDetection outlier_detection = 19;getOutlierDetection in interface ClusterOrBuilderpublic Cluster.Builder setOutlierDetection(OutlierDetection value)
If specified, outlier detection will be enabled for this upstream cluster. Each of the configuration values can be overridden via :ref:`runtime values <config_cluster_manager_cluster_runtime_outlier_detection>`.
.envoy.config.cluster.v4alpha.OutlierDetection outlier_detection = 19;public Cluster.Builder setOutlierDetection(OutlierDetection.Builder builderForValue)
If specified, outlier detection will be enabled for this upstream cluster. Each of the configuration values can be overridden via :ref:`runtime values <config_cluster_manager_cluster_runtime_outlier_detection>`.
.envoy.config.cluster.v4alpha.OutlierDetection outlier_detection = 19;public Cluster.Builder mergeOutlierDetection(OutlierDetection value)
If specified, outlier detection will be enabled for this upstream cluster. Each of the configuration values can be overridden via :ref:`runtime values <config_cluster_manager_cluster_runtime_outlier_detection>`.
.envoy.config.cluster.v4alpha.OutlierDetection outlier_detection = 19;public Cluster.Builder clearOutlierDetection()
If specified, outlier detection will be enabled for this upstream cluster. Each of the configuration values can be overridden via :ref:`runtime values <config_cluster_manager_cluster_runtime_outlier_detection>`.
.envoy.config.cluster.v4alpha.OutlierDetection outlier_detection = 19;public OutlierDetection.Builder getOutlierDetectionBuilder()
If specified, outlier detection will be enabled for this upstream cluster. Each of the configuration values can be overridden via :ref:`runtime values <config_cluster_manager_cluster_runtime_outlier_detection>`.
.envoy.config.cluster.v4alpha.OutlierDetection outlier_detection = 19;public OutlierDetectionOrBuilder getOutlierDetectionOrBuilder()
If specified, outlier detection will be enabled for this upstream cluster. Each of the configuration values can be overridden via :ref:`runtime values <config_cluster_manager_cluster_runtime_outlier_detection>`.
.envoy.config.cluster.v4alpha.OutlierDetection outlier_detection = 19;getOutlierDetectionOrBuilder in interface ClusterOrBuilderpublic boolean hasCleanupInterval()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`. Hosts are considered stale if they have not been used as upstream destinations during this interval. New hosts are added to original destination clusters on demand as new connections are redirected to Envoy, causing the number of hosts in the cluster to grow over time. Hosts that are not stale (they are actively used as destinations) are kept in the cluster, which allows connections to them remain open, saving the latency that would otherwise be spent on opening new connections. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }hasCleanupInterval in interface ClusterOrBuilderpublic com.google.protobuf.Duration getCleanupInterval()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`. Hosts are considered stale if they have not been used as upstream destinations during this interval. New hosts are added to original destination clusters on demand as new connections are redirected to Envoy, causing the number of hosts in the cluster to grow over time. Hosts that are not stale (they are actively used as destinations) are kept in the cluster, which allows connections to them remain open, saving the latency that would otherwise be spent on opening new connections. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }getCleanupInterval in interface ClusterOrBuilderpublic Cluster.Builder setCleanupInterval(com.google.protobuf.Duration value)
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`. Hosts are considered stale if they have not been used as upstream destinations during this interval. New hosts are added to original destination clusters on demand as new connections are redirected to Envoy, causing the number of hosts in the cluster to grow over time. Hosts that are not stale (they are actively used as destinations) are kept in the cluster, which allows connections to them remain open, saving the latency that would otherwise be spent on opening new connections. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }public Cluster.Builder setCleanupInterval(com.google.protobuf.Duration.Builder builderForValue)
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`. Hosts are considered stale if they have not been used as upstream destinations during this interval. New hosts are added to original destination clusters on demand as new connections are redirected to Envoy, causing the number of hosts in the cluster to grow over time. Hosts that are not stale (they are actively used as destinations) are kept in the cluster, which allows connections to them remain open, saving the latency that would otherwise be spent on opening new connections. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }public Cluster.Builder mergeCleanupInterval(com.google.protobuf.Duration value)
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`. Hosts are considered stale if they have not been used as upstream destinations during this interval. New hosts are added to original destination clusters on demand as new connections are redirected to Envoy, causing the number of hosts in the cluster to grow over time. Hosts that are not stale (they are actively used as destinations) are kept in the cluster, which allows connections to them remain open, saving the latency that would otherwise be spent on opening new connections. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }public Cluster.Builder clearCleanupInterval()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`. Hosts are considered stale if they have not been used as upstream destinations during this interval. New hosts are added to original destination clusters on demand as new connections are redirected to Envoy, causing the number of hosts in the cluster to grow over time. Hosts that are not stale (they are actively used as destinations) are kept in the cluster, which allows connections to them remain open, saving the latency that would otherwise be spent on opening new connections. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }public com.google.protobuf.Duration.Builder getCleanupIntervalBuilder()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`. Hosts are considered stale if they have not been used as upstream destinations during this interval. New hosts are added to original destination clusters on demand as new connections are redirected to Envoy, causing the number of hosts in the cluster to grow over time. Hosts that are not stale (they are actively used as destinations) are kept in the cluster, which allows connections to them remain open, saving the latency that would otherwise be spent on opening new connections. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }public com.google.protobuf.DurationOrBuilder getCleanupIntervalOrBuilder()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>`. Hosts are considered stale if they have not been used as upstream destinations during this interval. New hosts are added to original destination clusters on demand as new connections are redirected to Envoy, causing the number of hosts in the cluster to grow over time. Hosts that are not stale (they are actively used as destinations) are kept in the cluster, which allows connections to them remain open, saving the latency that would otherwise be spent on opening new connections. If this setting is not specified, the value defaults to 5000ms. For cluster types other than :ref:`ORIGINAL_DST<envoy_api_enum_value_config.cluster.v4alpha.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }getCleanupIntervalOrBuilder in interface ClusterOrBuilderpublic boolean hasUpstreamBindConfig()
Optional configuration used to bind newly established upstream connections. This overrides any bind_config specified in the bootstrap proto. If the address and port are empty, no bind will be performed.
.envoy.config.core.v4alpha.BindConfig upstream_bind_config = 21;hasUpstreamBindConfig in interface ClusterOrBuilderpublic BindConfig getUpstreamBindConfig()
Optional configuration used to bind newly established upstream connections. This overrides any bind_config specified in the bootstrap proto. If the address and port are empty, no bind will be performed.
.envoy.config.core.v4alpha.BindConfig upstream_bind_config = 21;getUpstreamBindConfig in interface ClusterOrBuilderpublic Cluster.Builder setUpstreamBindConfig(BindConfig value)
Optional configuration used to bind newly established upstream connections. This overrides any bind_config specified in the bootstrap proto. If the address and port are empty, no bind will be performed.
.envoy.config.core.v4alpha.BindConfig upstream_bind_config = 21;public Cluster.Builder setUpstreamBindConfig(BindConfig.Builder builderForValue)
Optional configuration used to bind newly established upstream connections. This overrides any bind_config specified in the bootstrap proto. If the address and port are empty, no bind will be performed.
.envoy.config.core.v4alpha.BindConfig upstream_bind_config = 21;public Cluster.Builder mergeUpstreamBindConfig(BindConfig value)
Optional configuration used to bind newly established upstream connections. This overrides any bind_config specified in the bootstrap proto. If the address and port are empty, no bind will be performed.
.envoy.config.core.v4alpha.BindConfig upstream_bind_config = 21;public Cluster.Builder clearUpstreamBindConfig()
Optional configuration used to bind newly established upstream connections. This overrides any bind_config specified in the bootstrap proto. If the address and port are empty, no bind will be performed.
.envoy.config.core.v4alpha.BindConfig upstream_bind_config = 21;public BindConfig.Builder getUpstreamBindConfigBuilder()
Optional configuration used to bind newly established upstream connections. This overrides any bind_config specified in the bootstrap proto. If the address and port are empty, no bind will be performed.
.envoy.config.core.v4alpha.BindConfig upstream_bind_config = 21;public BindConfigOrBuilder getUpstreamBindConfigOrBuilder()
Optional configuration used to bind newly established upstream connections. This overrides any bind_config specified in the bootstrap proto. If the address and port are empty, no bind will be performed.
.envoy.config.core.v4alpha.BindConfig upstream_bind_config = 21;getUpstreamBindConfigOrBuilder in interface ClusterOrBuilderpublic boolean hasLbSubsetConfig()
Configuration for load balancing subsetting.
.envoy.config.cluster.v4alpha.Cluster.LbSubsetConfig lb_subset_config = 22;hasLbSubsetConfig in interface ClusterOrBuilderpublic Cluster.LbSubsetConfig getLbSubsetConfig()
Configuration for load balancing subsetting.
.envoy.config.cluster.v4alpha.Cluster.LbSubsetConfig lb_subset_config = 22;getLbSubsetConfig in interface ClusterOrBuilderpublic Cluster.Builder setLbSubsetConfig(Cluster.LbSubsetConfig value)
Configuration for load balancing subsetting.
.envoy.config.cluster.v4alpha.Cluster.LbSubsetConfig lb_subset_config = 22;public Cluster.Builder setLbSubsetConfig(Cluster.LbSubsetConfig.Builder builderForValue)
Configuration for load balancing subsetting.
.envoy.config.cluster.v4alpha.Cluster.LbSubsetConfig lb_subset_config = 22;public Cluster.Builder mergeLbSubsetConfig(Cluster.LbSubsetConfig value)
Configuration for load balancing subsetting.
.envoy.config.cluster.v4alpha.Cluster.LbSubsetConfig lb_subset_config = 22;public Cluster.Builder clearLbSubsetConfig()
Configuration for load balancing subsetting.
.envoy.config.cluster.v4alpha.Cluster.LbSubsetConfig lb_subset_config = 22;public Cluster.LbSubsetConfig.Builder getLbSubsetConfigBuilder()
Configuration for load balancing subsetting.
.envoy.config.cluster.v4alpha.Cluster.LbSubsetConfig lb_subset_config = 22;public Cluster.LbSubsetConfigOrBuilder getLbSubsetConfigOrBuilder()
Configuration for load balancing subsetting.
.envoy.config.cluster.v4alpha.Cluster.LbSubsetConfig lb_subset_config = 22;getLbSubsetConfigOrBuilder in interface ClusterOrBuilderpublic boolean hasRingHashLbConfig()
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.RingHashLbConfig ring_hash_lb_config = 23;hasRingHashLbConfig in interface ClusterOrBuilderpublic Cluster.RingHashLbConfig getRingHashLbConfig()
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.RingHashLbConfig ring_hash_lb_config = 23;getRingHashLbConfig in interface ClusterOrBuilderpublic Cluster.Builder setRingHashLbConfig(Cluster.RingHashLbConfig value)
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.RingHashLbConfig ring_hash_lb_config = 23;public Cluster.Builder setRingHashLbConfig(Cluster.RingHashLbConfig.Builder builderForValue)
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.RingHashLbConfig ring_hash_lb_config = 23;public Cluster.Builder mergeRingHashLbConfig(Cluster.RingHashLbConfig value)
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.RingHashLbConfig ring_hash_lb_config = 23;public Cluster.Builder clearRingHashLbConfig()
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.RingHashLbConfig ring_hash_lb_config = 23;public Cluster.RingHashLbConfig.Builder getRingHashLbConfigBuilder()
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.RingHashLbConfig ring_hash_lb_config = 23;public Cluster.RingHashLbConfigOrBuilder getRingHashLbConfigOrBuilder()
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.RingHashLbConfig ring_hash_lb_config = 23;getRingHashLbConfigOrBuilder in interface ClusterOrBuilderpublic boolean hasMaglevLbConfig()
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.MaglevLbConfig maglev_lb_config = 52;hasMaglevLbConfig in interface ClusterOrBuilderpublic Cluster.MaglevLbConfig getMaglevLbConfig()
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.MaglevLbConfig maglev_lb_config = 52;getMaglevLbConfig in interface ClusterOrBuilderpublic Cluster.Builder setMaglevLbConfig(Cluster.MaglevLbConfig value)
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.MaglevLbConfig maglev_lb_config = 52;public Cluster.Builder setMaglevLbConfig(Cluster.MaglevLbConfig.Builder builderForValue)
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.MaglevLbConfig maglev_lb_config = 52;public Cluster.Builder mergeMaglevLbConfig(Cluster.MaglevLbConfig value)
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.MaglevLbConfig maglev_lb_config = 52;public Cluster.Builder clearMaglevLbConfig()
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.MaglevLbConfig maglev_lb_config = 52;public Cluster.MaglevLbConfig.Builder getMaglevLbConfigBuilder()
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.MaglevLbConfig maglev_lb_config = 52;public Cluster.MaglevLbConfigOrBuilder getMaglevLbConfigOrBuilder()
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.MaglevLbConfig maglev_lb_config = 52;getMaglevLbConfigOrBuilder in interface ClusterOrBuilderpublic boolean hasOriginalDstLbConfig()
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;hasOriginalDstLbConfig in interface ClusterOrBuilderpublic Cluster.OriginalDstLbConfig getOriginalDstLbConfig()
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;getOriginalDstLbConfig in interface ClusterOrBuilderpublic Cluster.Builder setOriginalDstLbConfig(Cluster.OriginalDstLbConfig value)
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;public Cluster.Builder setOriginalDstLbConfig(Cluster.OriginalDstLbConfig.Builder builderForValue)
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;public Cluster.Builder mergeOriginalDstLbConfig(Cluster.OriginalDstLbConfig value)
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;public Cluster.Builder clearOriginalDstLbConfig()
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;public Cluster.OriginalDstLbConfig.Builder getOriginalDstLbConfigBuilder()
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;public Cluster.OriginalDstLbConfigOrBuilder getOriginalDstLbConfigOrBuilder()
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;getOriginalDstLbConfigOrBuilder in interface ClusterOrBuilderpublic boolean hasLeastRequestLbConfig()
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.LeastRequestLbConfig least_request_lb_config = 37;hasLeastRequestLbConfig in interface ClusterOrBuilderpublic Cluster.LeastRequestLbConfig getLeastRequestLbConfig()
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.LeastRequestLbConfig least_request_lb_config = 37;getLeastRequestLbConfig in interface ClusterOrBuilderpublic Cluster.Builder setLeastRequestLbConfig(Cluster.LeastRequestLbConfig value)
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.LeastRequestLbConfig least_request_lb_config = 37;public Cluster.Builder setLeastRequestLbConfig(Cluster.LeastRequestLbConfig.Builder builderForValue)
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.LeastRequestLbConfig least_request_lb_config = 37;public Cluster.Builder mergeLeastRequestLbConfig(Cluster.LeastRequestLbConfig value)
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.LeastRequestLbConfig least_request_lb_config = 37;public Cluster.Builder clearLeastRequestLbConfig()
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.LeastRequestLbConfig least_request_lb_config = 37;public Cluster.LeastRequestLbConfig.Builder getLeastRequestLbConfigBuilder()
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.LeastRequestLbConfig least_request_lb_config = 37;public Cluster.LeastRequestLbConfigOrBuilder getLeastRequestLbConfigOrBuilder()
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v4alpha.Cluster.LeastRequestLbConfig least_request_lb_config = 37;getLeastRequestLbConfigOrBuilder in interface ClusterOrBuilderpublic boolean hasCommonLbConfig()
Common configuration for all load balancer implementations.
.envoy.config.cluster.v4alpha.Cluster.CommonLbConfig common_lb_config = 27;hasCommonLbConfig in interface ClusterOrBuilderpublic Cluster.CommonLbConfig getCommonLbConfig()
Common configuration for all load balancer implementations.
.envoy.config.cluster.v4alpha.Cluster.CommonLbConfig common_lb_config = 27;getCommonLbConfig in interface ClusterOrBuilderpublic Cluster.Builder setCommonLbConfig(Cluster.CommonLbConfig value)
Common configuration for all load balancer implementations.
.envoy.config.cluster.v4alpha.Cluster.CommonLbConfig common_lb_config = 27;public Cluster.Builder setCommonLbConfig(Cluster.CommonLbConfig.Builder builderForValue)
Common configuration for all load balancer implementations.
.envoy.config.cluster.v4alpha.Cluster.CommonLbConfig common_lb_config = 27;public Cluster.Builder mergeCommonLbConfig(Cluster.CommonLbConfig value)
Common configuration for all load balancer implementations.
.envoy.config.cluster.v4alpha.Cluster.CommonLbConfig common_lb_config = 27;public Cluster.Builder clearCommonLbConfig()
Common configuration for all load balancer implementations.
.envoy.config.cluster.v4alpha.Cluster.CommonLbConfig common_lb_config = 27;public Cluster.CommonLbConfig.Builder getCommonLbConfigBuilder()
Common configuration for all load balancer implementations.
.envoy.config.cluster.v4alpha.Cluster.CommonLbConfig common_lb_config = 27;public Cluster.CommonLbConfigOrBuilder getCommonLbConfigOrBuilder()
Common configuration for all load balancer implementations.
.envoy.config.cluster.v4alpha.Cluster.CommonLbConfig common_lb_config = 27;getCommonLbConfigOrBuilder in interface ClusterOrBuilderpublic boolean hasTransportSocket()
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name `tls` and :ref:`UpstreamTlsContexts <envoy_api_msg_extensions.transport_sockets.tls.v4alpha.UpstreamTlsContext>` in the `typed_config`. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v4alpha.TransportSocket transport_socket = 24;hasTransportSocket in interface ClusterOrBuilderpublic TransportSocket getTransportSocket()
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name `tls` and :ref:`UpstreamTlsContexts <envoy_api_msg_extensions.transport_sockets.tls.v4alpha.UpstreamTlsContext>` in the `typed_config`. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v4alpha.TransportSocket transport_socket = 24;getTransportSocket in interface ClusterOrBuilderpublic Cluster.Builder setTransportSocket(TransportSocket value)
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name `tls` and :ref:`UpstreamTlsContexts <envoy_api_msg_extensions.transport_sockets.tls.v4alpha.UpstreamTlsContext>` in the `typed_config`. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v4alpha.TransportSocket transport_socket = 24;public Cluster.Builder setTransportSocket(TransportSocket.Builder builderForValue)
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name `tls` and :ref:`UpstreamTlsContexts <envoy_api_msg_extensions.transport_sockets.tls.v4alpha.UpstreamTlsContext>` in the `typed_config`. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v4alpha.TransportSocket transport_socket = 24;public Cluster.Builder mergeTransportSocket(TransportSocket value)
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name `tls` and :ref:`UpstreamTlsContexts <envoy_api_msg_extensions.transport_sockets.tls.v4alpha.UpstreamTlsContext>` in the `typed_config`. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v4alpha.TransportSocket transport_socket = 24;public Cluster.Builder clearTransportSocket()
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name `tls` and :ref:`UpstreamTlsContexts <envoy_api_msg_extensions.transport_sockets.tls.v4alpha.UpstreamTlsContext>` in the `typed_config`. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v4alpha.TransportSocket transport_socket = 24;public TransportSocket.Builder getTransportSocketBuilder()
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name `tls` and :ref:`UpstreamTlsContexts <envoy_api_msg_extensions.transport_sockets.tls.v4alpha.UpstreamTlsContext>` in the `typed_config`. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v4alpha.TransportSocket transport_socket = 24;public TransportSocketOrBuilder getTransportSocketOrBuilder()
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name `tls` and :ref:`UpstreamTlsContexts <envoy_api_msg_extensions.transport_sockets.tls.v4alpha.UpstreamTlsContext>` in the `typed_config`. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v4alpha.TransportSocket transport_socket = 24;getTransportSocketOrBuilder in interface ClusterOrBuilderpublic boolean hasMetadata()
The Metadata field can be used to provide additional information about the cluster. It can be used for stats, logging, and varying filter behavior. Fields should use reverse DNS notation to denote which entity within Envoy will need the information. For instance, if the metadata is intended for the Router filter, the filter name should be specified as *envoy.filters.http.router*.
.envoy.config.core.v4alpha.Metadata metadata = 25;hasMetadata in interface ClusterOrBuilderpublic Metadata getMetadata()
The Metadata field can be used to provide additional information about the cluster. It can be used for stats, logging, and varying filter behavior. Fields should use reverse DNS notation to denote which entity within Envoy will need the information. For instance, if the metadata is intended for the Router filter, the filter name should be specified as *envoy.filters.http.router*.
.envoy.config.core.v4alpha.Metadata metadata = 25;getMetadata in interface ClusterOrBuilderpublic Cluster.Builder setMetadata(Metadata value)
The Metadata field can be used to provide additional information about the cluster. It can be used for stats, logging, and varying filter behavior. Fields should use reverse DNS notation to denote which entity within Envoy will need the information. For instance, if the metadata is intended for the Router filter, the filter name should be specified as *envoy.filters.http.router*.
.envoy.config.core.v4alpha.Metadata metadata = 25;public Cluster.Builder setMetadata(Metadata.Builder builderForValue)
The Metadata field can be used to provide additional information about the cluster. It can be used for stats, logging, and varying filter behavior. Fields should use reverse DNS notation to denote which entity within Envoy will need the information. For instance, if the metadata is intended for the Router filter, the filter name should be specified as *envoy.filters.http.router*.
.envoy.config.core.v4alpha.Metadata metadata = 25;public Cluster.Builder mergeMetadata(Metadata value)
The Metadata field can be used to provide additional information about the cluster. It can be used for stats, logging, and varying filter behavior. Fields should use reverse DNS notation to denote which entity within Envoy will need the information. For instance, if the metadata is intended for the Router filter, the filter name should be specified as *envoy.filters.http.router*.
.envoy.config.core.v4alpha.Metadata metadata = 25;public Cluster.Builder clearMetadata()
The Metadata field can be used to provide additional information about the cluster. It can be used for stats, logging, and varying filter behavior. Fields should use reverse DNS notation to denote which entity within Envoy will need the information. For instance, if the metadata is intended for the Router filter, the filter name should be specified as *envoy.filters.http.router*.
.envoy.config.core.v4alpha.Metadata metadata = 25;public Metadata.Builder getMetadataBuilder()
The Metadata field can be used to provide additional information about the cluster. It can be used for stats, logging, and varying filter behavior. Fields should use reverse DNS notation to denote which entity within Envoy will need the information. For instance, if the metadata is intended for the Router filter, the filter name should be specified as *envoy.filters.http.router*.
.envoy.config.core.v4alpha.Metadata metadata = 25;public MetadataOrBuilder getMetadataOrBuilder()
The Metadata field can be used to provide additional information about the cluster. It can be used for stats, logging, and varying filter behavior. Fields should use reverse DNS notation to denote which entity within Envoy will need the information. For instance, if the metadata is intended for the Router filter, the filter name should be specified as *envoy.filters.http.router*.
.envoy.config.core.v4alpha.Metadata metadata = 25;getMetadataOrBuilder in interface ClusterOrBuilderpublic boolean hasUpstreamConnectionOptions()
Optional options for upstream connections.
.envoy.config.cluster.v4alpha.UpstreamConnectionOptions upstream_connection_options = 30;hasUpstreamConnectionOptions in interface ClusterOrBuilderpublic UpstreamConnectionOptions getUpstreamConnectionOptions()
Optional options for upstream connections.
.envoy.config.cluster.v4alpha.UpstreamConnectionOptions upstream_connection_options = 30;getUpstreamConnectionOptions in interface ClusterOrBuilderpublic Cluster.Builder setUpstreamConnectionOptions(UpstreamConnectionOptions value)
Optional options for upstream connections.
.envoy.config.cluster.v4alpha.UpstreamConnectionOptions upstream_connection_options = 30;public Cluster.Builder setUpstreamConnectionOptions(UpstreamConnectionOptions.Builder builderForValue)
Optional options for upstream connections.
.envoy.config.cluster.v4alpha.UpstreamConnectionOptions upstream_connection_options = 30;public Cluster.Builder mergeUpstreamConnectionOptions(UpstreamConnectionOptions value)
Optional options for upstream connections.
.envoy.config.cluster.v4alpha.UpstreamConnectionOptions upstream_connection_options = 30;public Cluster.Builder clearUpstreamConnectionOptions()
Optional options for upstream connections.
.envoy.config.cluster.v4alpha.UpstreamConnectionOptions upstream_connection_options = 30;public UpstreamConnectionOptions.Builder getUpstreamConnectionOptionsBuilder()
Optional options for upstream connections.
.envoy.config.cluster.v4alpha.UpstreamConnectionOptions upstream_connection_options = 30;public UpstreamConnectionOptionsOrBuilder getUpstreamConnectionOptionsOrBuilder()
Optional options for upstream connections.
.envoy.config.cluster.v4alpha.UpstreamConnectionOptions upstream_connection_options = 30;getUpstreamConnectionOptionsOrBuilder in interface ClusterOrBuilderpublic boolean getCloseConnectionsOnHostHealthFailure()
If an upstream host becomes unhealthy (as determined by the configured health checks or outlier detection), immediately close all connections to the failed host. .. note:: This is currently only supported for connections created by tcp_proxy. .. note:: The current implementation of this feature closes all connections immediately when the unhealthy status is detected. If there are a large number of connections open to an upstream host that becomes unhealthy, Envoy may spend a substantial amount of time exclusively closing these connections, and not processing any other traffic.
bool close_connections_on_host_health_failure = 31;getCloseConnectionsOnHostHealthFailure in interface ClusterOrBuilderpublic Cluster.Builder setCloseConnectionsOnHostHealthFailure(boolean value)
If an upstream host becomes unhealthy (as determined by the configured health checks or outlier detection), immediately close all connections to the failed host. .. note:: This is currently only supported for connections created by tcp_proxy. .. note:: The current implementation of this feature closes all connections immediately when the unhealthy status is detected. If there are a large number of connections open to an upstream host that becomes unhealthy, Envoy may spend a substantial amount of time exclusively closing these connections, and not processing any other traffic.
bool close_connections_on_host_health_failure = 31;public Cluster.Builder clearCloseConnectionsOnHostHealthFailure()
If an upstream host becomes unhealthy (as determined by the configured health checks or outlier detection), immediately close all connections to the failed host. .. note:: This is currently only supported for connections created by tcp_proxy. .. note:: The current implementation of this feature closes all connections immediately when the unhealthy status is detected. If there are a large number of connections open to an upstream host that becomes unhealthy, Envoy may spend a substantial amount of time exclusively closing these connections, and not processing any other traffic.
bool close_connections_on_host_health_failure = 31;public boolean getIgnoreHealthOnHostRemoval()
If set to true, Envoy will ignore the health value of a host when processing its removal from service discovery. This means that if active health checking is used, Envoy will *not* wait for the endpoint to go unhealthy before removing it.
bool ignore_health_on_host_removal = 32;getIgnoreHealthOnHostRemoval in interface ClusterOrBuilderpublic Cluster.Builder setIgnoreHealthOnHostRemoval(boolean value)
If set to true, Envoy will ignore the health value of a host when processing its removal from service discovery. This means that if active health checking is used, Envoy will *not* wait for the endpoint to go unhealthy before removing it.
bool ignore_health_on_host_removal = 32;public Cluster.Builder clearIgnoreHealthOnHostRemoval()
If set to true, Envoy will ignore the health value of a host when processing its removal from service discovery. This means that if active health checking is used, Envoy will *not* wait for the endpoint to go unhealthy before removing it.
bool ignore_health_on_host_removal = 32;public List<Filter> getFiltersList()
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;getFiltersList in interface ClusterOrBuilderpublic int getFiltersCount()
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;getFiltersCount in interface ClusterOrBuilderpublic Filter getFilters(int index)
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;getFilters in interface ClusterOrBuilderpublic Cluster.Builder setFilters(int index, Filter value)
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;public Cluster.Builder setFilters(int index, Filter.Builder builderForValue)
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;public Cluster.Builder addFilters(Filter value)
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;public Cluster.Builder addFilters(int index, Filter value)
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;public Cluster.Builder addFilters(Filter.Builder builderForValue)
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;public Cluster.Builder addFilters(int index, Filter.Builder builderForValue)
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;public Cluster.Builder addAllFilters(Iterable<? extends Filter> values)
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;public Cluster.Builder clearFilters()
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;public Cluster.Builder removeFilters(int index)
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;public Filter.Builder getFiltersBuilder(int index)
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;public FilterOrBuilder getFiltersOrBuilder(int index)
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;getFiltersOrBuilder in interface ClusterOrBuilderpublic List<? extends FilterOrBuilder> getFiltersOrBuilderList()
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;getFiltersOrBuilderList in interface ClusterOrBuilderpublic Filter.Builder addFiltersBuilder()
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;public Filter.Builder addFiltersBuilder(int index)
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;public List<Filter.Builder> getFiltersBuilderList()
An (optional) network filter chain, listed in the order the filters should be applied. The chain will be applied to all outgoing connections that Envoy makes to the upstream servers of this cluster.
repeated .envoy.config.cluster.v4alpha.Filter filters = 40;public boolean hasLoadBalancingPolicy()
[#not-implemented-hide:] New mechanism for LB policy configuration. Used only if the :ref:`lb_policy<envoy_api_field_config.cluster.v4alpha.Cluster.lb_policy>` field has the value :ref:`LOAD_BALANCING_POLICY_CONFIG<envoy_api_enum_value_config.cluster.v4alpha.Cluster.LbPolicy.LOAD_BALANCING_POLICY_CONFIG>`.
.envoy.config.cluster.v4alpha.LoadBalancingPolicy load_balancing_policy = 41;hasLoadBalancingPolicy in interface ClusterOrBuilderpublic LoadBalancingPolicy getLoadBalancingPolicy()
[#not-implemented-hide:] New mechanism for LB policy configuration. Used only if the :ref:`lb_policy<envoy_api_field_config.cluster.v4alpha.Cluster.lb_policy>` field has the value :ref:`LOAD_BALANCING_POLICY_CONFIG<envoy_api_enum_value_config.cluster.v4alpha.Cluster.LbPolicy.LOAD_BALANCING_POLICY_CONFIG>`.
.envoy.config.cluster.v4alpha.LoadBalancingPolicy load_balancing_policy = 41;getLoadBalancingPolicy in interface ClusterOrBuilderpublic Cluster.Builder setLoadBalancingPolicy(LoadBalancingPolicy value)
[#not-implemented-hide:] New mechanism for LB policy configuration. Used only if the :ref:`lb_policy<envoy_api_field_config.cluster.v4alpha.Cluster.lb_policy>` field has the value :ref:`LOAD_BALANCING_POLICY_CONFIG<envoy_api_enum_value_config.cluster.v4alpha.Cluster.LbPolicy.LOAD_BALANCING_POLICY_CONFIG>`.
.envoy.config.cluster.v4alpha.LoadBalancingPolicy load_balancing_policy = 41;public Cluster.Builder setLoadBalancingPolicy(LoadBalancingPolicy.Builder builderForValue)
[#not-implemented-hide:] New mechanism for LB policy configuration. Used only if the :ref:`lb_policy<envoy_api_field_config.cluster.v4alpha.Cluster.lb_policy>` field has the value :ref:`LOAD_BALANCING_POLICY_CONFIG<envoy_api_enum_value_config.cluster.v4alpha.Cluster.LbPolicy.LOAD_BALANCING_POLICY_CONFIG>`.
.envoy.config.cluster.v4alpha.LoadBalancingPolicy load_balancing_policy = 41;public Cluster.Builder mergeLoadBalancingPolicy(LoadBalancingPolicy value)
[#not-implemented-hide:] New mechanism for LB policy configuration. Used only if the :ref:`lb_policy<envoy_api_field_config.cluster.v4alpha.Cluster.lb_policy>` field has the value :ref:`LOAD_BALANCING_POLICY_CONFIG<envoy_api_enum_value_config.cluster.v4alpha.Cluster.LbPolicy.LOAD_BALANCING_POLICY_CONFIG>`.
.envoy.config.cluster.v4alpha.LoadBalancingPolicy load_balancing_policy = 41;public Cluster.Builder clearLoadBalancingPolicy()
[#not-implemented-hide:] New mechanism for LB policy configuration. Used only if the :ref:`lb_policy<envoy_api_field_config.cluster.v4alpha.Cluster.lb_policy>` field has the value :ref:`LOAD_BALANCING_POLICY_CONFIG<envoy_api_enum_value_config.cluster.v4alpha.Cluster.LbPolicy.LOAD_BALANCING_POLICY_CONFIG>`.
.envoy.config.cluster.v4alpha.LoadBalancingPolicy load_balancing_policy = 41;public LoadBalancingPolicy.Builder getLoadBalancingPolicyBuilder()
[#not-implemented-hide:] New mechanism for LB policy configuration. Used only if the :ref:`lb_policy<envoy_api_field_config.cluster.v4alpha.Cluster.lb_policy>` field has the value :ref:`LOAD_BALANCING_POLICY_CONFIG<envoy_api_enum_value_config.cluster.v4alpha.Cluster.LbPolicy.LOAD_BALANCING_POLICY_CONFIG>`.
.envoy.config.cluster.v4alpha.LoadBalancingPolicy load_balancing_policy = 41;public LoadBalancingPolicyOrBuilder getLoadBalancingPolicyOrBuilder()
[#not-implemented-hide:] New mechanism for LB policy configuration. Used only if the :ref:`lb_policy<envoy_api_field_config.cluster.v4alpha.Cluster.lb_policy>` field has the value :ref:`LOAD_BALANCING_POLICY_CONFIG<envoy_api_enum_value_config.cluster.v4alpha.Cluster.LbPolicy.LOAD_BALANCING_POLICY_CONFIG>`.
.envoy.config.cluster.v4alpha.LoadBalancingPolicy load_balancing_policy = 41;getLoadBalancingPolicyOrBuilder in interface ClusterOrBuilderpublic boolean hasLrsServer()
[#not-implemented-hide:] If present, tells the client where to send load reports via LRS. If not present, the client will fall back to a client-side default, which may be either (a) don't send any load reports or (b) send load reports for all clusters to a single default server (which may be configured in the bootstrap file). Note that if multiple clusters point to the same LRS server, the client may choose to create a separate stream for each cluster or it may choose to coalesce the data for multiple clusters onto a single stream. Either way, the client must make sure to send the data for any given cluster on no more than one stream. [#next-major-version: In the v3 API, we should consider restructuring this somehow, maybe by allowing LRS to go on the ADS stream, or maybe by moving some of the negotiation from the LRS stream here.]
.envoy.config.core.v4alpha.ConfigSource lrs_server = 42;hasLrsServer in interface ClusterOrBuilderpublic ConfigSource getLrsServer()
[#not-implemented-hide:] If present, tells the client where to send load reports via LRS. If not present, the client will fall back to a client-side default, which may be either (a) don't send any load reports or (b) send load reports for all clusters to a single default server (which may be configured in the bootstrap file). Note that if multiple clusters point to the same LRS server, the client may choose to create a separate stream for each cluster or it may choose to coalesce the data for multiple clusters onto a single stream. Either way, the client must make sure to send the data for any given cluster on no more than one stream. [#next-major-version: In the v3 API, we should consider restructuring this somehow, maybe by allowing LRS to go on the ADS stream, or maybe by moving some of the negotiation from the LRS stream here.]
.envoy.config.core.v4alpha.ConfigSource lrs_server = 42;getLrsServer in interface ClusterOrBuilderpublic Cluster.Builder setLrsServer(ConfigSource value)
[#not-implemented-hide:] If present, tells the client where to send load reports via LRS. If not present, the client will fall back to a client-side default, which may be either (a) don't send any load reports or (b) send load reports for all clusters to a single default server (which may be configured in the bootstrap file). Note that if multiple clusters point to the same LRS server, the client may choose to create a separate stream for each cluster or it may choose to coalesce the data for multiple clusters onto a single stream. Either way, the client must make sure to send the data for any given cluster on no more than one stream. [#next-major-version: In the v3 API, we should consider restructuring this somehow, maybe by allowing LRS to go on the ADS stream, or maybe by moving some of the negotiation from the LRS stream here.]
.envoy.config.core.v4alpha.ConfigSource lrs_server = 42;public Cluster.Builder setLrsServer(ConfigSource.Builder builderForValue)
[#not-implemented-hide:] If present, tells the client where to send load reports via LRS. If not present, the client will fall back to a client-side default, which may be either (a) don't send any load reports or (b) send load reports for all clusters to a single default server (which may be configured in the bootstrap file). Note that if multiple clusters point to the same LRS server, the client may choose to create a separate stream for each cluster or it may choose to coalesce the data for multiple clusters onto a single stream. Either way, the client must make sure to send the data for any given cluster on no more than one stream. [#next-major-version: In the v3 API, we should consider restructuring this somehow, maybe by allowing LRS to go on the ADS stream, or maybe by moving some of the negotiation from the LRS stream here.]
.envoy.config.core.v4alpha.ConfigSource lrs_server = 42;public Cluster.Builder mergeLrsServer(ConfigSource value)
[#not-implemented-hide:] If present, tells the client where to send load reports via LRS. If not present, the client will fall back to a client-side default, which may be either (a) don't send any load reports or (b) send load reports for all clusters to a single default server (which may be configured in the bootstrap file). Note that if multiple clusters point to the same LRS server, the client may choose to create a separate stream for each cluster or it may choose to coalesce the data for multiple clusters onto a single stream. Either way, the client must make sure to send the data for any given cluster on no more than one stream. [#next-major-version: In the v3 API, we should consider restructuring this somehow, maybe by allowing LRS to go on the ADS stream, or maybe by moving some of the negotiation from the LRS stream here.]
.envoy.config.core.v4alpha.ConfigSource lrs_server = 42;public Cluster.Builder clearLrsServer()
[#not-implemented-hide:] If present, tells the client where to send load reports via LRS. If not present, the client will fall back to a client-side default, which may be either (a) don't send any load reports or (b) send load reports for all clusters to a single default server (which may be configured in the bootstrap file). Note that if multiple clusters point to the same LRS server, the client may choose to create a separate stream for each cluster or it may choose to coalesce the data for multiple clusters onto a single stream. Either way, the client must make sure to send the data for any given cluster on no more than one stream. [#next-major-version: In the v3 API, we should consider restructuring this somehow, maybe by allowing LRS to go on the ADS stream, or maybe by moving some of the negotiation from the LRS stream here.]
.envoy.config.core.v4alpha.ConfigSource lrs_server = 42;public ConfigSource.Builder getLrsServerBuilder()
[#not-implemented-hide:] If present, tells the client where to send load reports via LRS. If not present, the client will fall back to a client-side default, which may be either (a) don't send any load reports or (b) send load reports for all clusters to a single default server (which may be configured in the bootstrap file). Note that if multiple clusters point to the same LRS server, the client may choose to create a separate stream for each cluster or it may choose to coalesce the data for multiple clusters onto a single stream. Either way, the client must make sure to send the data for any given cluster on no more than one stream. [#next-major-version: In the v3 API, we should consider restructuring this somehow, maybe by allowing LRS to go on the ADS stream, or maybe by moving some of the negotiation from the LRS stream here.]
.envoy.config.core.v4alpha.ConfigSource lrs_server = 42;public ConfigSourceOrBuilder getLrsServerOrBuilder()
[#not-implemented-hide:] If present, tells the client where to send load reports via LRS. If not present, the client will fall back to a client-side default, which may be either (a) don't send any load reports or (b) send load reports for all clusters to a single default server (which may be configured in the bootstrap file). Note that if multiple clusters point to the same LRS server, the client may choose to create a separate stream for each cluster or it may choose to coalesce the data for multiple clusters onto a single stream. Either way, the client must make sure to send the data for any given cluster on no more than one stream. [#next-major-version: In the v3 API, we should consider restructuring this somehow, maybe by allowing LRS to go on the ADS stream, or maybe by moving some of the negotiation from the LRS stream here.]
.envoy.config.core.v4alpha.ConfigSource lrs_server = 42;getLrsServerOrBuilder in interface ClusterOrBuilderpublic boolean hasUpstreamConfig()
Optional customization and configuration of upstream connection pool, and upstream type. Currently this field only applies for HTTP traffic but is designed for eventual use for custom TCP upstreams. For HTTP traffic, Envoy will generally take downstream HTTP and send it upstream as upstream HTTP, using the http connection pool and the codec from `http2_protocol_options` For routes where CONNECT termination is configured, Envoy will take downstream CONNECT requests and forward the CONNECT payload upstream over raw TCP using the tcp connection pool. The default pool used is the generic connection pool which creates the HTTP upstream for most HTTP requests, and the TCP upstream if CONNECT termination is configured. If users desire custom connection pool or upstream behavior, for example terminating CONNECT only if a custom filter indicates it is appropriate, the custom factories can be registered and configured here.
.envoy.config.core.v4alpha.TypedExtensionConfig upstream_config = 48;hasUpstreamConfig in interface ClusterOrBuilderpublic TypedExtensionConfig getUpstreamConfig()
Optional customization and configuration of upstream connection pool, and upstream type. Currently this field only applies for HTTP traffic but is designed for eventual use for custom TCP upstreams. For HTTP traffic, Envoy will generally take downstream HTTP and send it upstream as upstream HTTP, using the http connection pool and the codec from `http2_protocol_options` For routes where CONNECT termination is configured, Envoy will take downstream CONNECT requests and forward the CONNECT payload upstream over raw TCP using the tcp connection pool. The default pool used is the generic connection pool which creates the HTTP upstream for most HTTP requests, and the TCP upstream if CONNECT termination is configured. If users desire custom connection pool or upstream behavior, for example terminating CONNECT only if a custom filter indicates it is appropriate, the custom factories can be registered and configured here.
.envoy.config.core.v4alpha.TypedExtensionConfig upstream_config = 48;getUpstreamConfig in interface ClusterOrBuilderpublic Cluster.Builder setUpstreamConfig(TypedExtensionConfig value)
Optional customization and configuration of upstream connection pool, and upstream type. Currently this field only applies for HTTP traffic but is designed for eventual use for custom TCP upstreams. For HTTP traffic, Envoy will generally take downstream HTTP and send it upstream as upstream HTTP, using the http connection pool and the codec from `http2_protocol_options` For routes where CONNECT termination is configured, Envoy will take downstream CONNECT requests and forward the CONNECT payload upstream over raw TCP using the tcp connection pool. The default pool used is the generic connection pool which creates the HTTP upstream for most HTTP requests, and the TCP upstream if CONNECT termination is configured. If users desire custom connection pool or upstream behavior, for example terminating CONNECT only if a custom filter indicates it is appropriate, the custom factories can be registered and configured here.
.envoy.config.core.v4alpha.TypedExtensionConfig upstream_config = 48;public Cluster.Builder setUpstreamConfig(TypedExtensionConfig.Builder builderForValue)
Optional customization and configuration of upstream connection pool, and upstream type. Currently this field only applies for HTTP traffic but is designed for eventual use for custom TCP upstreams. For HTTP traffic, Envoy will generally take downstream HTTP and send it upstream as upstream HTTP, using the http connection pool and the codec from `http2_protocol_options` For routes where CONNECT termination is configured, Envoy will take downstream CONNECT requests and forward the CONNECT payload upstream over raw TCP using the tcp connection pool. The default pool used is the generic connection pool which creates the HTTP upstream for most HTTP requests, and the TCP upstream if CONNECT termination is configured. If users desire custom connection pool or upstream behavior, for example terminating CONNECT only if a custom filter indicates it is appropriate, the custom factories can be registered and configured here.
.envoy.config.core.v4alpha.TypedExtensionConfig upstream_config = 48;public Cluster.Builder mergeUpstreamConfig(TypedExtensionConfig value)
Optional customization and configuration of upstream connection pool, and upstream type. Currently this field only applies for HTTP traffic but is designed for eventual use for custom TCP upstreams. For HTTP traffic, Envoy will generally take downstream HTTP and send it upstream as upstream HTTP, using the http connection pool and the codec from `http2_protocol_options` For routes where CONNECT termination is configured, Envoy will take downstream CONNECT requests and forward the CONNECT payload upstream over raw TCP using the tcp connection pool. The default pool used is the generic connection pool which creates the HTTP upstream for most HTTP requests, and the TCP upstream if CONNECT termination is configured. If users desire custom connection pool or upstream behavior, for example terminating CONNECT only if a custom filter indicates it is appropriate, the custom factories can be registered and configured here.
.envoy.config.core.v4alpha.TypedExtensionConfig upstream_config = 48;public Cluster.Builder clearUpstreamConfig()
Optional customization and configuration of upstream connection pool, and upstream type. Currently this field only applies for HTTP traffic but is designed for eventual use for custom TCP upstreams. For HTTP traffic, Envoy will generally take downstream HTTP and send it upstream as upstream HTTP, using the http connection pool and the codec from `http2_protocol_options` For routes where CONNECT termination is configured, Envoy will take downstream CONNECT requests and forward the CONNECT payload upstream over raw TCP using the tcp connection pool. The default pool used is the generic connection pool which creates the HTTP upstream for most HTTP requests, and the TCP upstream if CONNECT termination is configured. If users desire custom connection pool or upstream behavior, for example terminating CONNECT only if a custom filter indicates it is appropriate, the custom factories can be registered and configured here.
.envoy.config.core.v4alpha.TypedExtensionConfig upstream_config = 48;public TypedExtensionConfig.Builder getUpstreamConfigBuilder()
Optional customization and configuration of upstream connection pool, and upstream type. Currently this field only applies for HTTP traffic but is designed for eventual use for custom TCP upstreams. For HTTP traffic, Envoy will generally take downstream HTTP and send it upstream as upstream HTTP, using the http connection pool and the codec from `http2_protocol_options` For routes where CONNECT termination is configured, Envoy will take downstream CONNECT requests and forward the CONNECT payload upstream over raw TCP using the tcp connection pool. The default pool used is the generic connection pool which creates the HTTP upstream for most HTTP requests, and the TCP upstream if CONNECT termination is configured. If users desire custom connection pool or upstream behavior, for example terminating CONNECT only if a custom filter indicates it is appropriate, the custom factories can be registered and configured here.
.envoy.config.core.v4alpha.TypedExtensionConfig upstream_config = 48;public TypedExtensionConfigOrBuilder getUpstreamConfigOrBuilder()
Optional customization and configuration of upstream connection pool, and upstream type. Currently this field only applies for HTTP traffic but is designed for eventual use for custom TCP upstreams. For HTTP traffic, Envoy will generally take downstream HTTP and send it upstream as upstream HTTP, using the http connection pool and the codec from `http2_protocol_options` For routes where CONNECT termination is configured, Envoy will take downstream CONNECT requests and forward the CONNECT payload upstream over raw TCP using the tcp connection pool. The default pool used is the generic connection pool which creates the HTTP upstream for most HTTP requests, and the TCP upstream if CONNECT termination is configured. If users desire custom connection pool or upstream behavior, for example terminating CONNECT only if a custom filter indicates it is appropriate, the custom factories can be registered and configured here.
.envoy.config.core.v4alpha.TypedExtensionConfig upstream_config = 48;getUpstreamConfigOrBuilder in interface ClusterOrBuilderpublic boolean hasTrackClusterStats()
Configuration to track optional cluster stats.
.envoy.config.cluster.v4alpha.TrackClusterStats track_cluster_stats = 49;hasTrackClusterStats in interface ClusterOrBuilderpublic TrackClusterStats getTrackClusterStats()
Configuration to track optional cluster stats.
.envoy.config.cluster.v4alpha.TrackClusterStats track_cluster_stats = 49;getTrackClusterStats in interface ClusterOrBuilderpublic Cluster.Builder setTrackClusterStats(TrackClusterStats value)
Configuration to track optional cluster stats.
.envoy.config.cluster.v4alpha.TrackClusterStats track_cluster_stats = 49;public Cluster.Builder setTrackClusterStats(TrackClusterStats.Builder builderForValue)
Configuration to track optional cluster stats.
.envoy.config.cluster.v4alpha.TrackClusterStats track_cluster_stats = 49;public Cluster.Builder mergeTrackClusterStats(TrackClusterStats value)
Configuration to track optional cluster stats.
.envoy.config.cluster.v4alpha.TrackClusterStats track_cluster_stats = 49;public Cluster.Builder clearTrackClusterStats()
Configuration to track optional cluster stats.
.envoy.config.cluster.v4alpha.TrackClusterStats track_cluster_stats = 49;public TrackClusterStats.Builder getTrackClusterStatsBuilder()
Configuration to track optional cluster stats.
.envoy.config.cluster.v4alpha.TrackClusterStats track_cluster_stats = 49;public TrackClusterStatsOrBuilder getTrackClusterStatsOrBuilder()
Configuration to track optional cluster stats.
.envoy.config.cluster.v4alpha.TrackClusterStats track_cluster_stats = 49;getTrackClusterStatsOrBuilder in interface ClusterOrBuilderpublic boolean hasPreconnectPolicy()
[#not-implemented-hide:] Preconnect configuration for this cluster.
.envoy.config.cluster.v4alpha.Cluster.PreconnectPolicy preconnect_policy = 50;hasPreconnectPolicy in interface ClusterOrBuilderpublic Cluster.PreconnectPolicy getPreconnectPolicy()
[#not-implemented-hide:] Preconnect configuration for this cluster.
.envoy.config.cluster.v4alpha.Cluster.PreconnectPolicy preconnect_policy = 50;getPreconnectPolicy in interface ClusterOrBuilderpublic Cluster.Builder setPreconnectPolicy(Cluster.PreconnectPolicy value)
[#not-implemented-hide:] Preconnect configuration for this cluster.
.envoy.config.cluster.v4alpha.Cluster.PreconnectPolicy preconnect_policy = 50;public Cluster.Builder setPreconnectPolicy(Cluster.PreconnectPolicy.Builder builderForValue)
[#not-implemented-hide:] Preconnect configuration for this cluster.
.envoy.config.cluster.v4alpha.Cluster.PreconnectPolicy preconnect_policy = 50;public Cluster.Builder mergePreconnectPolicy(Cluster.PreconnectPolicy value)
[#not-implemented-hide:] Preconnect configuration for this cluster.
.envoy.config.cluster.v4alpha.Cluster.PreconnectPolicy preconnect_policy = 50;public Cluster.Builder clearPreconnectPolicy()
[#not-implemented-hide:] Preconnect configuration for this cluster.
.envoy.config.cluster.v4alpha.Cluster.PreconnectPolicy preconnect_policy = 50;public Cluster.PreconnectPolicy.Builder getPreconnectPolicyBuilder()
[#not-implemented-hide:] Preconnect configuration for this cluster.
.envoy.config.cluster.v4alpha.Cluster.PreconnectPolicy preconnect_policy = 50;public Cluster.PreconnectPolicyOrBuilder getPreconnectPolicyOrBuilder()
[#not-implemented-hide:] Preconnect configuration for this cluster.
.envoy.config.cluster.v4alpha.Cluster.PreconnectPolicy preconnect_policy = 50;getPreconnectPolicyOrBuilder in interface ClusterOrBuilderpublic boolean getConnectionPoolPerDownstreamConnection()
If `connection_pool_per_downstream_connection` is true, the cluster will use a separate connection pool for every downstream connection
bool connection_pool_per_downstream_connection = 51;getConnectionPoolPerDownstreamConnection in interface ClusterOrBuilderpublic Cluster.Builder setConnectionPoolPerDownstreamConnection(boolean value)
If `connection_pool_per_downstream_connection` is true, the cluster will use a separate connection pool for every downstream connection
bool connection_pool_per_downstream_connection = 51;public Cluster.Builder clearConnectionPoolPerDownstreamConnection()
If `connection_pool_per_downstream_connection` is true, the cluster will use a separate connection pool for every downstream connection
bool connection_pool_per_downstream_connection = 51;public final Cluster.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
setUnknownFields in interface com.google.protobuf.Message.BuildersetUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>public final Cluster.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
mergeUnknownFields in interface com.google.protobuf.Message.BuildermergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<Cluster.Builder>Copyright © 2018–2021 The Envoy Project. All rights reserved.