Class Cluster.Builder
- java.lang.Object
-
- com.google.protobuf.AbstractMessageLite.Builder
-
- com.google.protobuf.AbstractMessage.Builder<BuilderT>
-
- com.google.protobuf.GeneratedMessage.Builder<Cluster.Builder>
-
- io.envoyproxy.envoy.config.cluster.v3.Cluster.Builder
-
- All Implemented Interfaces:
com.google.protobuf.Message.Builder
,com.google.protobuf.MessageLite.Builder
,com.google.protobuf.MessageLiteOrBuilder
,com.google.protobuf.MessageOrBuilder
,ClusterOrBuilder
,java.lang.Cloneable
- Enclosing class:
- Cluster
public static final class Cluster.Builder extends com.google.protobuf.GeneratedMessage.Builder<Cluster.Builder> implements ClusterOrBuilder
Configuration for a single upstream cluster. [#next-free-field: 57]
Protobuf typeenvoy.config.cluster.v3.Cluster
-
-
Nested Class Summary
Nested Classes Modifier and Type Class Description private static class
Cluster.Builder.TypedExtensionProtocolOptionsConverter
-
Field Summary
-
Method Summary
All Methods Static Methods Instance Methods Concrete Methods Deprecated Methods Modifier and Type Method Description Cluster.Builder
addAllDnsResolvers(java.lang.Iterable<? extends Address> values)
Deprecated.Cluster.Builder
addAllFilters(java.lang.Iterable<? extends Filter> values)
An (optional) network filter chain, listed in the order the filters should be applied.Cluster.Builder
addAllHealthChecks(java.lang.Iterable<? extends HealthCheck> values)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster.Cluster.Builder
addAllTransportSocketMatches(java.lang.Iterable<? extends Cluster.TransportSocketMatch> values)
Configuration to use different transport sockets for different endpoints.Cluster.Builder
addDnsResolvers(int index, Address value)
Deprecated.Cluster.Builder
addDnsResolvers(int index, Address.Builder builderForValue)
Deprecated.Cluster.Builder
addDnsResolvers(Address value)
Deprecated.Cluster.Builder
addDnsResolvers(Address.Builder builderForValue)
Deprecated.Address.Builder
addDnsResolversBuilder()
Deprecated.Address.Builder
addDnsResolversBuilder(int index)
Deprecated.Cluster.Builder
addFilters(int index, 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(Filter value)
An (optional) network filter chain, listed in the order the filters should be applied.Cluster.Builder
addFilters(Filter.Builder builderForValue)
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(int index, 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(HealthCheck value)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster.Cluster.Builder
addHealthChecks(HealthCheck.Builder builderForValue)
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
addTransportSocketMatches(int index, 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(Cluster.TransportSocketMatch value)
Configuration to use different transport sockets for different endpoints.Cluster.Builder
addTransportSocketMatches(Cluster.TransportSocketMatch.Builder builderForValue)
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()
private void
buildPartial0(Cluster result)
private void
buildPartial1(Cluster result)
private void
buildPartialOneofs(Cluster result)
private void
buildPartialRepeatedFields(Cluster result)
Cluster.Builder
clear()
Cluster.Builder
clearAltStatName()
An optional alternative to the cluster name to be used for observability.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_v3_api_enum_value_config.cluster.v3.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.Cluster.Builder
clearClusterDiscoveryType()
Cluster.Builder
clearClusterType()
The custom cluster type.Cluster.Builder
clearCommonHttpProtocolOptions()
Deprecated.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 connectionCluster.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate.Cluster.Builder
clearDnsResolutionConfig()
Deprecated.Cluster.Builder
clearDnsResolvers()
Deprecated.Cluster.Builder
clearEdsClusterConfig()
Configuration to use for EDS updates for the Cluster.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
clearHttp2ProtocolOptions()
Deprecated.Cluster.Builder
clearHttpProtocolOptions()
Deprecated.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.Cluster.Builder
clearLoadBalancingPolicy()
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.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()
Deprecated.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
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()
Preconnect configuration for this cluster.Cluster.Builder
clearProtocolSelection()
Deprecated.envoy.config.cluster.v3.Cluster.protocol_selection is deprecated.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
clearRoundRobinLbConfig()
Optional configuration for the RoundRobin load balancing policy.Cluster.Builder
clearTrackClusterStats()
Configuration to track optional cluster stats.Cluster.Builder
clearTrackTimeoutBudgets()
Deprecated.envoy.config.cluster.v3.Cluster.track_timeout_budgets is deprecated.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
clearTypedDnsResolverConfig()
DNS resolver type configuration extension.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
clearUpstreamHttpProtocolOptions()
Deprecated.Cluster.Builder
clearUseTcpForDnsLookups()
Deprecated.envoy.config.cluster.v3.Cluster.use_tcp_for_dns_lookups is deprecated.Cluster.Builder
clearWaitForWarmOnInit()
Optional configuration for having cluster readiness block on warm-up.boolean
containsTypedExtensionProtocolOptions(java.lang.String key)
The extension_protocol_options field is used to provide extension-specific protocol options for upstream connections.private void
ensureDnsResolversIsMutable()
private void
ensureFiltersIsMutable()
private void
ensureHealthChecksIsMutable()
private void
ensureTransportSocketMatchesIsMutable()
java.lang.String
getAltStatName()
An optional alternative to the cluster name to be used for observability.com.google.protobuf.ByteString
getAltStatNameBytes()
An optional alternative to the cluster name to be used for observability.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.private com.google.protobuf.SingleFieldBuilder<CircuitBreakers,CircuitBreakers.Builder,CircuitBreakersOrBuilder>
getCircuitBreakersFieldBuilder()
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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>`.com.google.protobuf.Duration.Builder
getCleanupIntervalBuilder()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>`.private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder,com.google.protobuf.DurationOrBuilder>
getCleanupIntervalFieldBuilder()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>`.com.google.protobuf.DurationOrBuilder
getCleanupIntervalOrBuilder()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.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.Cluster.ClusterDiscoveryTypeCase
getClusterDiscoveryTypeCase()
Cluster.CustomClusterType
getClusterType()
The custom cluster type.Cluster.CustomClusterType.Builder
getClusterTypeBuilder()
The custom cluster type.private com.google.protobuf.SingleFieldBuilder<Cluster.CustomClusterType,Cluster.CustomClusterType.Builder,Cluster.CustomClusterTypeOrBuilder>
getClusterTypeFieldBuilder()
The custom cluster type.Cluster.CustomClusterTypeOrBuilder
getClusterTypeOrBuilder()
The custom cluster type.HttpProtocolOptions
getCommonHttpProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.common_http_protocol_options is deprecated.HttpProtocolOptions.Builder
getCommonHttpProtocolOptionsBuilder()
Deprecated.private com.google.protobuf.SingleFieldBuilder<HttpProtocolOptions,HttpProtocolOptions.Builder,HttpProtocolOptionsOrBuilder>
getCommonHttpProtocolOptionsFieldBuilder()
Additional options when handling HTTP requests upstream.HttpProtocolOptionsOrBuilder
getCommonHttpProtocolOptionsOrBuilder()
Deprecated.Cluster.CommonLbConfig
getCommonLbConfig()
Common configuration for all load balancer implementations.Cluster.CommonLbConfig.Builder
getCommonLbConfigBuilder()
Common configuration for all load balancer implementations.private com.google.protobuf.SingleFieldBuilder<Cluster.CommonLbConfig,Cluster.CommonLbConfig.Builder,Cluster.CommonLbConfigOrBuilder>
getCommonLbConfigFieldBuilder()
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 connectioncom.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.private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder,com.google.protobuf.DurationOrBuilder>
getConnectTimeoutFieldBuilder()
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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, this is used as the cluster’s DNS refresh rate when requests are failing.private com.google.protobuf.SingleFieldBuilder<Cluster.RefreshRate,Cluster.RefreshRate.Builder,Cluster.RefreshRateOrBuilder>
getDnsFailureRefreshRateFieldBuilder()
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate.private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder,com.google.protobuf.DurationOrBuilder>
getDnsRefreshRateFieldBuilder()
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate.DnsResolutionConfig
getDnsResolutionConfig()
Deprecated.envoy.config.cluster.v3.Cluster.dns_resolution_config is deprecated.DnsResolutionConfig.Builder
getDnsResolutionConfigBuilder()
Deprecated.private com.google.protobuf.SingleFieldBuilder<DnsResolutionConfig,DnsResolutionConfig.Builder,DnsResolutionConfigOrBuilder>
getDnsResolutionConfigFieldBuilder()
DNS resolution configuration which includes the underlying dns resolver addresses and options.DnsResolutionConfigOrBuilder
getDnsResolutionConfigOrBuilder()
Deprecated.Address
getDnsResolvers(int index)
Deprecated.Address.Builder
getDnsResolversBuilder(int index)
Deprecated.java.util.List<Address.Builder>
getDnsResolversBuilderList()
Deprecated.int
getDnsResolversCount()
Deprecated.private com.google.protobuf.RepeatedFieldBuilder<Address,Address.Builder,AddressOrBuilder>
getDnsResolversFieldBuilder()
java.util.List<Address>
getDnsResolversList()
Deprecated.AddressOrBuilder
getDnsResolversOrBuilder(int index)
Deprecated.java.util.List<? extends AddressOrBuilder>
getDnsResolversOrBuilderList()
Deprecated.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.private com.google.protobuf.SingleFieldBuilder<Cluster.EdsClusterConfig,Cluster.EdsClusterConfig.Builder,Cluster.EdsClusterConfigOrBuilder>
getEdsClusterConfigFieldBuilder()
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.java.util.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.private com.google.protobuf.RepeatedFieldBuilder<Filter,Filter.Builder,FilterOrBuilder>
getFiltersFieldBuilder()
java.util.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.java.util.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.java.util.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.private com.google.protobuf.RepeatedFieldBuilder<HealthCheck,HealthCheck.Builder,HealthCheckOrBuilder>
getHealthChecksFieldBuilder()
java.util.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.java.util.List<? extends HealthCheckOrBuilder>
getHealthChecksOrBuilderList()
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster.Http2ProtocolOptions
getHttp2ProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.http2_protocol_options is deprecated.Http2ProtocolOptions.Builder
getHttp2ProtocolOptionsBuilder()
Deprecated.private com.google.protobuf.SingleFieldBuilder<Http2ProtocolOptions,Http2ProtocolOptions.Builder,Http2ProtocolOptionsOrBuilder>
getHttp2ProtocolOptionsFieldBuilder()
Even if default HTTP2 protocol options are desired, this field must be set so that Envoy will assume that the upstream supports HTTP/2 when making new HTTP connection pool connections.Http2ProtocolOptionsOrBuilder
getHttp2ProtocolOptionsOrBuilder()
Deprecated.Http1ProtocolOptions
getHttpProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.http_protocol_options is deprecated.Http1ProtocolOptions.Builder
getHttpProtocolOptionsBuilder()
Deprecated.private com.google.protobuf.SingleFieldBuilder<Http1ProtocolOptions,Http1ProtocolOptions.Builder,Http1ProtocolOptionsOrBuilder>
getHttpProtocolOptionsFieldBuilder()
Additional options when handling HTTP1 requests.Http1ProtocolOptionsOrBuilder
getHttpProtocolOptionsOrBuilder()
Deprecated.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.private com.google.protobuf.SingleFieldBuilder<Cluster.LbSubsetConfig,Cluster.LbSubsetConfig.Builder,Cluster.LbSubsetConfigOrBuilder>
getLbSubsetConfigFieldBuilder()
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.private com.google.protobuf.SingleFieldBuilder<Cluster.LeastRequestLbConfig,Cluster.LeastRequestLbConfig.Builder,Cluster.LeastRequestLbConfigOrBuilder>
getLeastRequestLbConfigFieldBuilder()
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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.ClusterLoadAssignment.Builder
getLoadAssignmentBuilder()
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.private com.google.protobuf.SingleFieldBuilder<ClusterLoadAssignment,ClusterLoadAssignment.Builder,ClusterLoadAssignmentOrBuilder>
getLoadAssignmentFieldBuilder()
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.ClusterLoadAssignmentOrBuilder
getLoadAssignmentOrBuilder()
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.LoadBalancingPolicy
getLoadBalancingPolicy()
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.LoadBalancingPolicy.Builder
getLoadBalancingPolicyBuilder()
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.private com.google.protobuf.SingleFieldBuilder<LoadBalancingPolicy,LoadBalancingPolicy.Builder,LoadBalancingPolicyOrBuilder>
getLoadBalancingPolicyFieldBuilder()
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.LoadBalancingPolicyOrBuilder
getLoadBalancingPolicyOrBuilder()
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.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.private com.google.protobuf.SingleFieldBuilder<ConfigSource,ConfigSource.Builder,ConfigSourceOrBuilder>
getLrsServerFieldBuilder()
[#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.private com.google.protobuf.SingleFieldBuilder<Cluster.MaglevLbConfig,Cluster.MaglevLbConfig.Builder,Cluster.MaglevLbConfigOrBuilder>
getMaglevLbConfigFieldBuilder()
Optional configuration for the Maglev load balancing policy.Cluster.MaglevLbConfigOrBuilder
getMaglevLbConfigOrBuilder()
Optional configuration for the Maglev load balancing policy.com.google.protobuf.UInt32Value
getMaxRequestsPerConnection()
Deprecated.envoy.config.cluster.v3.Cluster.max_requests_per_connection is deprecated.com.google.protobuf.UInt32Value.Builder
getMaxRequestsPerConnectionBuilder()
Deprecated.private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,com.google.protobuf.UInt32Value.Builder,com.google.protobuf.UInt32ValueOrBuilder>
getMaxRequestsPerConnectionFieldBuilder()
Optional maximum requests for a single upstream connection.com.google.protobuf.UInt32ValueOrBuilder
getMaxRequestsPerConnectionOrBuilder()
Deprecated.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.private com.google.protobuf.SingleFieldBuilder<Metadata,Metadata.Builder,MetadataOrBuilder>
getMetadataFieldBuilder()
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.java.util.Map<java.lang.String,com.google.protobuf.Any>
getMutableTypedExtensionProtocolOptions()
Deprecated.java.lang.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.private com.google.protobuf.SingleFieldBuilder<Cluster.OriginalDstLbConfig,Cluster.OriginalDstLbConfig.Builder,Cluster.OriginalDstLbConfigOrBuilder>
getOriginalDstLbConfigFieldBuilder()
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.private com.google.protobuf.SingleFieldBuilder<OutlierDetection,OutlierDetection.Builder,OutlierDetectionOrBuilder>
getOutlierDetectionFieldBuilder()
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.private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,com.google.protobuf.UInt32Value.Builder,com.google.protobuf.UInt32ValueOrBuilder>
getPerConnectionBufferLimitBytesFieldBuilder()
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()
Preconnect configuration for this cluster.Cluster.PreconnectPolicy.Builder
getPreconnectPolicyBuilder()
Preconnect configuration for this cluster.private com.google.protobuf.SingleFieldBuilder<Cluster.PreconnectPolicy,Cluster.PreconnectPolicy.Builder,Cluster.PreconnectPolicyOrBuilder>
getPreconnectPolicyFieldBuilder()
Preconnect configuration for this cluster.Cluster.PreconnectPolicyOrBuilder
getPreconnectPolicyOrBuilder()
Preconnect configuration for this cluster.Cluster.ClusterProtocolSelection
getProtocolSelection()
Deprecated.envoy.config.cluster.v3.Cluster.protocol_selection is deprecated.int
getProtocolSelectionValue()
Deprecated.envoy.config.cluster.v3.Cluster.protocol_selection is deprecated.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.private com.google.protobuf.SingleFieldBuilder<Cluster.RingHashLbConfig,Cluster.RingHashLbConfig.Builder,Cluster.RingHashLbConfigOrBuilder>
getRingHashLbConfigFieldBuilder()
Optional configuration for the Ring Hash load balancing policy.Cluster.RingHashLbConfigOrBuilder
getRingHashLbConfigOrBuilder()
Optional configuration for the Ring Hash load balancing policy.Cluster.RoundRobinLbConfig
getRoundRobinLbConfig()
Optional configuration for the RoundRobin load balancing policy.Cluster.RoundRobinLbConfig.Builder
getRoundRobinLbConfigBuilder()
Optional configuration for the RoundRobin load balancing policy.private com.google.protobuf.SingleFieldBuilder<Cluster.RoundRobinLbConfig,Cluster.RoundRobinLbConfig.Builder,Cluster.RoundRobinLbConfigOrBuilder>
getRoundRobinLbConfigFieldBuilder()
Optional configuration for the RoundRobin load balancing policy.Cluster.RoundRobinLbConfigOrBuilder
getRoundRobinLbConfigOrBuilder()
Optional configuration for the RoundRobin load balancing policy.TrackClusterStats
getTrackClusterStats()
Configuration to track optional cluster stats.TrackClusterStats.Builder
getTrackClusterStatsBuilder()
Configuration to track optional cluster stats.private com.google.protobuf.SingleFieldBuilder<TrackClusterStats,TrackClusterStats.Builder,TrackClusterStatsOrBuilder>
getTrackClusterStatsFieldBuilder()
Configuration to track optional cluster stats.TrackClusterStatsOrBuilder
getTrackClusterStatsOrBuilder()
Configuration to track optional cluster stats.boolean
getTrackTimeoutBudgets()
Deprecated.envoy.config.cluster.v3.Cluster.track_timeout_budgets is deprecated.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.private com.google.protobuf.SingleFieldBuilder<TransportSocket,TransportSocket.Builder,TransportSocketOrBuilder>
getTransportSocketFieldBuilder()
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.java.util.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.private com.google.protobuf.RepeatedFieldBuilder<Cluster.TransportSocketMatch,Cluster.TransportSocketMatch.Builder,Cluster.TransportSocketMatchOrBuilder>
getTransportSocketMatchesFieldBuilder()
java.util.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.java.util.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.TypedExtensionConfig
getTypedDnsResolverConfig()
DNS resolver type configuration extension.TypedExtensionConfig.Builder
getTypedDnsResolverConfigBuilder()
DNS resolver type configuration extension.private com.google.protobuf.SingleFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder,TypedExtensionConfigOrBuilder>
getTypedDnsResolverConfigFieldBuilder()
DNS resolver type configuration extension.TypedExtensionConfigOrBuilder
getTypedDnsResolverConfigOrBuilder()
DNS resolver type configuration extension.java.util.Map<java.lang.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.java.util.Map<java.lang.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(java.lang.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(java.lang.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.private com.google.protobuf.SingleFieldBuilder<BindConfig,BindConfig.Builder,BindConfigOrBuilder>
getUpstreamBindConfigFieldBuilder()
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.private com.google.protobuf.SingleFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder,TypedExtensionConfigOrBuilder>
getUpstreamConfigFieldBuilder()
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.private com.google.protobuf.SingleFieldBuilder<UpstreamConnectionOptions,UpstreamConnectionOptions.Builder,UpstreamConnectionOptionsOrBuilder>
getUpstreamConnectionOptionsFieldBuilder()
Optional options for upstream connections.UpstreamConnectionOptionsOrBuilder
getUpstreamConnectionOptionsOrBuilder()
Optional options for upstream connections.UpstreamHttpProtocolOptions
getUpstreamHttpProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.upstream_http_protocol_options is deprecated.UpstreamHttpProtocolOptions.Builder
getUpstreamHttpProtocolOptionsBuilder()
Deprecated.private com.google.protobuf.SingleFieldBuilder<UpstreamHttpProtocolOptions,UpstreamHttpProtocolOptions.Builder,UpstreamHttpProtocolOptionsOrBuilder>
getUpstreamHttpProtocolOptionsFieldBuilder()
HTTP protocol options that are applied only to upstream HTTP connections.UpstreamHttpProtocolOptionsOrBuilder
getUpstreamHttpProtocolOptionsOrBuilder()
Deprecated.boolean
getUseTcpForDnsLookups()
Deprecated.envoy.config.cluster.v3.Cluster.use_tcp_for_dns_lookups is deprecated.com.google.protobuf.BoolValue
getWaitForWarmOnInit()
Optional configuration for having cluster readiness block on warm-up.com.google.protobuf.BoolValue.Builder
getWaitForWarmOnInitBuilder()
Optional configuration for having cluster readiness block on warm-up.private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder,com.google.protobuf.BoolValueOrBuilder>
getWaitForWarmOnInitFieldBuilder()
Optional configuration for having cluster readiness block on warm-up.com.google.protobuf.BoolValueOrBuilder
getWaitForWarmOnInitOrBuilder()
Optional configuration for having cluster readiness block on warm-up.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>`.boolean
hasClusterType()
The custom cluster type.boolean
hasCommonHttpProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.common_http_protocol_options is deprecated.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate.boolean
hasDnsResolutionConfig()
Deprecated.envoy.config.cluster.v3.Cluster.dns_resolution_config is deprecated.boolean
hasEdsClusterConfig()
Configuration to use for EDS updates for the Cluster.boolean
hasHttp2ProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.http2_protocol_options is deprecated.boolean
hasHttpProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.http_protocol_options is deprecated.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.boolean
hasLoadBalancingPolicy()
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.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()
Deprecated.envoy.config.cluster.v3.Cluster.max_requests_per_connection is deprecated.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()
Preconnect configuration for this cluster.boolean
hasRingHashLbConfig()
Optional configuration for the Ring Hash load balancing policy.boolean
hasRoundRobinLbConfig()
Optional configuration for the RoundRobin load balancing policy.boolean
hasTrackClusterStats()
Configuration to track optional cluster stats.boolean
hasTransportSocket()
Optional custom transport socket implementation to use for upstream connections.boolean
hasType()
The :ref:`service discovery type <arch_overview_service_discovery_types>` to use for resolving the cluster.boolean
hasTypedDnsResolverConfig()
DNS resolver type configuration extension.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.boolean
hasUpstreamHttpProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.upstream_http_protocol_options is deprecated.boolean
hasWaitForWarmOnInit()
Optional configuration for having cluster readiness block on warm-up.protected com.google.protobuf.GeneratedMessage.FieldAccessorTable
internalGetFieldAccessorTable()
protected com.google.protobuf.MapFieldReflectionAccessor
internalGetMapFieldReflection(int number)
protected com.google.protobuf.MapFieldReflectionAccessor
internalGetMutableMapFieldReflection(int number)
private com.google.protobuf.MapFieldBuilder<java.lang.String,com.google.protobuf.AnyOrBuilder,com.google.protobuf.Any,com.google.protobuf.Any.Builder>
internalGetMutableTypedExtensionProtocolOptions()
private com.google.protobuf.MapFieldBuilder<java.lang.String,com.google.protobuf.AnyOrBuilder,com.google.protobuf.Any,com.google.protobuf.Any.Builder>
internalGetTypedExtensionProtocolOptions()
boolean
isInitialized()
private void
maybeForceBuilderInitialization()
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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>`.Cluster.Builder
mergeClusterType(Cluster.CustomClusterType value)
The custom cluster type.Cluster.Builder
mergeCommonHttpProtocolOptions(HttpProtocolOptions value)
Deprecated.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate.Cluster.Builder
mergeDnsResolutionConfig(DnsResolutionConfig value)
Deprecated.Cluster.Builder
mergeEdsClusterConfig(Cluster.EdsClusterConfig value)
Configuration to use for EDS updates for the Cluster.Cluster.Builder
mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry)
Cluster.Builder
mergeFrom(com.google.protobuf.Message other)
Cluster.Builder
mergeFrom(Cluster other)
Cluster.Builder
mergeHttp2ProtocolOptions(Http2ProtocolOptions value)
Deprecated.Cluster.Builder
mergeHttpProtocolOptions(Http1ProtocolOptions value)
Deprecated.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.Cluster.Builder
mergeLoadBalancingPolicy(LoadBalancingPolicy value)
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.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)
Deprecated.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)
Preconnect configuration for this cluster.Cluster.Builder
mergeRingHashLbConfig(Cluster.RingHashLbConfig value)
Optional configuration for the Ring Hash load balancing policy.Cluster.Builder
mergeRoundRobinLbConfig(Cluster.RoundRobinLbConfig value)
Optional configuration for the RoundRobin 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
mergeTypedDnsResolverConfig(TypedExtensionConfig value)
DNS resolver type configuration extension.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
mergeUpstreamHttpProtocolOptions(UpstreamHttpProtocolOptions value)
Deprecated.Cluster.Builder
mergeWaitForWarmOnInit(com.google.protobuf.BoolValue value)
Optional configuration for having cluster readiness block on warm-up.Cluster.Builder
putAllTypedExtensionProtocolOptions(java.util.Map<java.lang.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(java.lang.String key, com.google.protobuf.Any value)
The extension_protocol_options field is used to provide extension-specific protocol options for upstream connections.com.google.protobuf.Any.Builder
putTypedExtensionProtocolOptionsBuilderIfAbsent(java.lang.String key)
The extension_protocol_options field is used to provide extension-specific protocol options for upstream connections.Cluster.Builder
removeDnsResolvers(int index)
Deprecated.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(java.lang.String key)
The extension_protocol_options field is used to provide extension-specific protocol options for upstream connections.Cluster.Builder
setAltStatName(java.lang.String value)
An optional alternative to the cluster name to be used for observability.Cluster.Builder
setAltStatNameBytes(com.google.protobuf.ByteString value)
An optional alternative to the cluster name to be used for observability.Cluster.Builder
setCircuitBreakers(CircuitBreakers value)
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.Cluster.Builder
setCircuitBreakers(CircuitBreakers.Builder builderForValue)
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.Cluster.Builder
setCleanupInterval(com.google.protobuf.Duration value)
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>`.Cluster.Builder
setCleanupInterval(com.google.protobuf.Duration.Builder builderForValue)
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.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.Cluster.Builder
setClusterType(Cluster.CustomClusterType value)
The custom cluster type.Cluster.Builder
setClusterType(Cluster.CustomClusterType.Builder builderForValue)
The custom cluster type.Cluster.Builder
setCommonHttpProtocolOptions(HttpProtocolOptions value)
Deprecated.Cluster.Builder
setCommonHttpProtocolOptions(HttpProtocolOptions.Builder builderForValue)
Deprecated.Cluster.Builder
setCommonLbConfig(Cluster.CommonLbConfig value)
Common configuration for all load balancer implementations.Cluster.Builder
setCommonLbConfig(Cluster.CommonLbConfig.Builder builderForValue)
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 connectionCluster.Builder
setConnectTimeout(com.google.protobuf.Duration value)
The timeout for new network connections to hosts in the cluster.Cluster.Builder
setConnectTimeout(com.google.protobuf.Duration.Builder builderForValue)
The timeout for new network connections to hosts in the cluster.Cluster.Builder
setDnsFailureRefreshRate(Cluster.RefreshRate value)
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, this is used as the cluster’s DNS refresh rate when requests are failing.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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 value)
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, this value is used as the cluster’s DNS refresh rate.Cluster.Builder
setDnsResolutionConfig(DnsResolutionConfig value)
Deprecated.Cluster.Builder
setDnsResolutionConfig(DnsResolutionConfig.Builder builderForValue)
Deprecated.Cluster.Builder
setDnsResolvers(int index, Address value)
Deprecated.Cluster.Builder
setDnsResolvers(int index, Address.Builder builderForValue)
Deprecated.Cluster.Builder
setEdsClusterConfig(Cluster.EdsClusterConfig value)
Configuration to use for EDS updates for the Cluster.Cluster.Builder
setEdsClusterConfig(Cluster.EdsClusterConfig.Builder builderForValue)
Configuration to use for EDS updates for the Cluster.Cluster.Builder
setFilters(int index, Filter value)
An (optional) network filter chain, listed in the order the filters should be applied.Cluster.Builder
setFilters(int index, Filter.Builder builderForValue)
An (optional) network filter chain, listed in the order the filters should be applied.Cluster.Builder
setHealthChecks(int index, HealthCheck value)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster.Cluster.Builder
setHealthChecks(int index, HealthCheck.Builder builderForValue)
Optional :ref:`active health checking <arch_overview_health_checking>` configuration for the cluster.Cluster.Builder
setHttp2ProtocolOptions(Http2ProtocolOptions value)
Deprecated.Cluster.Builder
setHttp2ProtocolOptions(Http2ProtocolOptions.Builder builderForValue)
Deprecated.Cluster.Builder
setHttpProtocolOptions(Http1ProtocolOptions value)
Deprecated.Cluster.Builder
setHttpProtocolOptions(Http1ProtocolOptions.Builder builderForValue)
Deprecated.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 value)
Configuration for load balancing subsetting.Cluster.Builder
setLbSubsetConfig(Cluster.LbSubsetConfig.Builder builderForValue)
Configuration for load balancing subsetting.Cluster.Builder
setLeastRequestLbConfig(Cluster.LeastRequestLbConfig value)
Optional configuration for the LeastRequest load balancing policy.Cluster.Builder
setLeastRequestLbConfig(Cluster.LeastRequestLbConfig.Builder builderForValue)
Optional configuration for the LeastRequest load balancing policy.Cluster.Builder
setLoadAssignment(ClusterLoadAssignment value)
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.Cluster.Builder
setLoadAssignment(ClusterLoadAssignment.Builder builderForValue)
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` clusters.Cluster.Builder
setLoadBalancingPolicy(LoadBalancingPolicy value)
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.Cluster.Builder
setLoadBalancingPolicy(LoadBalancingPolicy.Builder builderForValue)
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.Cluster.Builder
setLrsServer(ConfigSource value)
[#not-implemented-hide:] If present, tells the client where to send load reports via LRS.Cluster.Builder
setLrsServer(ConfigSource.Builder builderForValue)
[#not-implemented-hide:] If present, tells the client where to send load reports via LRS.Cluster.Builder
setMaglevLbConfig(Cluster.MaglevLbConfig value)
Optional configuration for the Maglev load balancing policy.Cluster.Builder
setMaglevLbConfig(Cluster.MaglevLbConfig.Builder builderForValue)
Optional configuration for the Maglev load balancing policy.Cluster.Builder
setMaxRequestsPerConnection(com.google.protobuf.UInt32Value value)
Deprecated.Cluster.Builder
setMaxRequestsPerConnection(com.google.protobuf.UInt32Value.Builder builderForValue)
Deprecated.Cluster.Builder
setMetadata(Metadata value)
The Metadata field can be used to provide additional information about the cluster.Cluster.Builder
setMetadata(Metadata.Builder builderForValue)
The Metadata field can be used to provide additional information about the cluster.Cluster.Builder
setName(java.lang.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 value)
Optional configuration for the Original Destination load balancing policy.Cluster.Builder
setOriginalDstLbConfig(Cluster.OriginalDstLbConfig.Builder builderForValue)
Optional configuration for the Original Destination load balancing policy.Cluster.Builder
setOutlierDetection(OutlierDetection value)
If specified, outlier detection will be enabled for this upstream cluster.Cluster.Builder
setOutlierDetection(OutlierDetection.Builder builderForValue)
If specified, outlier detection will be enabled for this upstream cluster.Cluster.Builder
setPerConnectionBufferLimitBytes(com.google.protobuf.UInt32Value value)
Soft limit on size of the cluster’s connections read and write buffers.Cluster.Builder
setPerConnectionBufferLimitBytes(com.google.protobuf.UInt32Value.Builder builderForValue)
Soft limit on size of the cluster’s connections read and write buffers.Cluster.Builder
setPreconnectPolicy(Cluster.PreconnectPolicy value)
Preconnect configuration for this cluster.Cluster.Builder
setPreconnectPolicy(Cluster.PreconnectPolicy.Builder builderForValue)
Preconnect configuration for this cluster.Cluster.Builder
setProtocolSelection(Cluster.ClusterProtocolSelection value)
Deprecated.envoy.config.cluster.v3.Cluster.protocol_selection is deprecated.Cluster.Builder
setProtocolSelectionValue(int value)
Deprecated.envoy.config.cluster.v3.Cluster.protocol_selection is deprecated.Cluster.Builder
setRespectDnsTtl(boolean value)
Optional configuration for setting cluster's DNS refresh rate.Cluster.Builder
setRingHashLbConfig(Cluster.RingHashLbConfig value)
Optional configuration for the Ring Hash load balancing policy.Cluster.Builder
setRingHashLbConfig(Cluster.RingHashLbConfig.Builder builderForValue)
Optional configuration for the Ring Hash load balancing policy.Cluster.Builder
setRoundRobinLbConfig(Cluster.RoundRobinLbConfig value)
Optional configuration for the RoundRobin load balancing policy.Cluster.Builder
setRoundRobinLbConfig(Cluster.RoundRobinLbConfig.Builder builderForValue)
Optional configuration for the RoundRobin load balancing policy.Cluster.Builder
setTrackClusterStats(TrackClusterStats value)
Configuration to track optional cluster stats.Cluster.Builder
setTrackClusterStats(TrackClusterStats.Builder builderForValue)
Configuration to track optional cluster stats.Cluster.Builder
setTrackTimeoutBudgets(boolean value)
Deprecated.envoy.config.cluster.v3.Cluster.track_timeout_budgets is deprecated.Cluster.Builder
setTransportSocket(TransportSocket value)
Optional custom transport socket implementation to use for upstream connections.Cluster.Builder
setTransportSocket(TransportSocket.Builder builderForValue)
Optional custom transport socket implementation to use for upstream connections.Cluster.Builder
setTransportSocketMatches(int index, Cluster.TransportSocketMatch value)
Configuration to use different transport sockets for different endpoints.Cluster.Builder
setTransportSocketMatches(int index, Cluster.TransportSocketMatch.Builder builderForValue)
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
setTypedDnsResolverConfig(TypedExtensionConfig value)
DNS resolver type configuration extension.Cluster.Builder
setTypedDnsResolverConfig(TypedExtensionConfig.Builder builderForValue)
DNS resolver type configuration extension.Cluster.Builder
setTypeValue(int value)
The :ref:`service discovery type <arch_overview_service_discovery_types>` to use for resolving the cluster.Cluster.Builder
setUpstreamBindConfig(BindConfig value)
Optional configuration used to bind newly established upstream connections.Cluster.Builder
setUpstreamBindConfig(BindConfig.Builder builderForValue)
Optional configuration used to bind newly established upstream connections.Cluster.Builder
setUpstreamConfig(TypedExtensionConfig value)
Optional customization and configuration of upstream connection pool, and upstream type.Cluster.Builder
setUpstreamConfig(TypedExtensionConfig.Builder builderForValue)
Optional customization and configuration of upstream connection pool, and upstream type.Cluster.Builder
setUpstreamConnectionOptions(UpstreamConnectionOptions value)
Optional options for upstream connections.Cluster.Builder
setUpstreamConnectionOptions(UpstreamConnectionOptions.Builder builderForValue)
Optional options for upstream connections.Cluster.Builder
setUpstreamHttpProtocolOptions(UpstreamHttpProtocolOptions value)
Deprecated.Cluster.Builder
setUpstreamHttpProtocolOptions(UpstreamHttpProtocolOptions.Builder builderForValue)
Deprecated.Cluster.Builder
setUseTcpForDnsLookups(boolean value)
Deprecated.envoy.config.cluster.v3.Cluster.use_tcp_for_dns_lookups is deprecated.Cluster.Builder
setWaitForWarmOnInit(com.google.protobuf.BoolValue value)
Optional configuration for having cluster readiness block on warm-up.Cluster.Builder
setWaitForWarmOnInit(com.google.protobuf.BoolValue.Builder builderForValue)
Optional configuration for having cluster readiness block on warm-up.-
Methods inherited from class com.google.protobuf.GeneratedMessage.Builder
addRepeatedField, clearField, clearOneof, clone, getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMutableMapField, isClean, markClean, mergeUnknownFields, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setField, setRepeatedField, setUnknownFields, setUnknownFieldSetBuilder, setUnknownFieldsProto3
-
Methods inherited from class com.google.protobuf.AbstractMessage.Builder
findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toString
-
Methods inherited from class com.google.protobuf.AbstractMessageLite.Builder
addAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageException
-
Methods inherited from class java.lang.Object
equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
-
-
-
-
Field Detail
-
clusterDiscoveryTypeCase_
private int clusterDiscoveryTypeCase_
-
clusterDiscoveryType_
private java.lang.Object clusterDiscoveryType_
-
lbConfigCase_
private int lbConfigCase_
-
lbConfig_
private java.lang.Object lbConfig_
-
bitField0_
private int bitField0_
-
bitField1_
private int bitField1_
-
transportSocketMatches_
private java.util.List<Cluster.TransportSocketMatch> transportSocketMatches_
-
transportSocketMatchesBuilder_
private com.google.protobuf.RepeatedFieldBuilder<Cluster.TransportSocketMatch,Cluster.TransportSocketMatch.Builder,Cluster.TransportSocketMatchOrBuilder> transportSocketMatchesBuilder_
-
name_
private java.lang.Object name_
-
altStatName_
private java.lang.Object altStatName_
-
clusterTypeBuilder_
private com.google.protobuf.SingleFieldBuilder<Cluster.CustomClusterType,Cluster.CustomClusterType.Builder,Cluster.CustomClusterTypeOrBuilder> clusterTypeBuilder_
-
edsClusterConfig_
private Cluster.EdsClusterConfig edsClusterConfig_
-
edsClusterConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<Cluster.EdsClusterConfig,Cluster.EdsClusterConfig.Builder,Cluster.EdsClusterConfigOrBuilder> edsClusterConfigBuilder_
-
connectTimeout_
private com.google.protobuf.Duration connectTimeout_
-
connectTimeoutBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder,com.google.protobuf.DurationOrBuilder> connectTimeoutBuilder_
-
perConnectionBufferLimitBytes_
private com.google.protobuf.UInt32Value perConnectionBufferLimitBytes_
-
perConnectionBufferLimitBytesBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,com.google.protobuf.UInt32Value.Builder,com.google.protobuf.UInt32ValueOrBuilder> perConnectionBufferLimitBytesBuilder_
-
lbPolicy_
private int lbPolicy_
-
loadAssignment_
private ClusterLoadAssignment loadAssignment_
-
loadAssignmentBuilder_
private com.google.protobuf.SingleFieldBuilder<ClusterLoadAssignment,ClusterLoadAssignment.Builder,ClusterLoadAssignmentOrBuilder> loadAssignmentBuilder_
-
healthChecks_
private java.util.List<HealthCheck> healthChecks_
-
healthChecksBuilder_
private com.google.protobuf.RepeatedFieldBuilder<HealthCheck,HealthCheck.Builder,HealthCheckOrBuilder> healthChecksBuilder_
-
maxRequestsPerConnection_
private com.google.protobuf.UInt32Value maxRequestsPerConnection_
-
maxRequestsPerConnectionBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,com.google.protobuf.UInt32Value.Builder,com.google.protobuf.UInt32ValueOrBuilder> maxRequestsPerConnectionBuilder_
-
circuitBreakers_
private CircuitBreakers circuitBreakers_
-
circuitBreakersBuilder_
private com.google.protobuf.SingleFieldBuilder<CircuitBreakers,CircuitBreakers.Builder,CircuitBreakersOrBuilder> circuitBreakersBuilder_
-
upstreamHttpProtocolOptions_
private UpstreamHttpProtocolOptions upstreamHttpProtocolOptions_
-
upstreamHttpProtocolOptionsBuilder_
private com.google.protobuf.SingleFieldBuilder<UpstreamHttpProtocolOptions,UpstreamHttpProtocolOptions.Builder,UpstreamHttpProtocolOptionsOrBuilder> upstreamHttpProtocolOptionsBuilder_
-
commonHttpProtocolOptions_
private HttpProtocolOptions commonHttpProtocolOptions_
-
commonHttpProtocolOptionsBuilder_
private com.google.protobuf.SingleFieldBuilder<HttpProtocolOptions,HttpProtocolOptions.Builder,HttpProtocolOptionsOrBuilder> commonHttpProtocolOptionsBuilder_
-
httpProtocolOptions_
private Http1ProtocolOptions httpProtocolOptions_
-
httpProtocolOptionsBuilder_
private com.google.protobuf.SingleFieldBuilder<Http1ProtocolOptions,Http1ProtocolOptions.Builder,Http1ProtocolOptionsOrBuilder> httpProtocolOptionsBuilder_
-
http2ProtocolOptions_
private Http2ProtocolOptions http2ProtocolOptions_
-
http2ProtocolOptionsBuilder_
private com.google.protobuf.SingleFieldBuilder<Http2ProtocolOptions,Http2ProtocolOptions.Builder,Http2ProtocolOptionsOrBuilder> http2ProtocolOptionsBuilder_
-
typedExtensionProtocolOptionsConverter
private static final Cluster.Builder.TypedExtensionProtocolOptionsConverter typedExtensionProtocolOptionsConverter
-
typedExtensionProtocolOptions_
private com.google.protobuf.MapFieldBuilder<java.lang.String,com.google.protobuf.AnyOrBuilder,com.google.protobuf.Any,com.google.protobuf.Any.Builder> typedExtensionProtocolOptions_
-
dnsRefreshRate_
private com.google.protobuf.Duration dnsRefreshRate_
-
dnsRefreshRateBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder,com.google.protobuf.DurationOrBuilder> dnsRefreshRateBuilder_
-
dnsFailureRefreshRate_
private Cluster.RefreshRate dnsFailureRefreshRate_
-
dnsFailureRefreshRateBuilder_
private com.google.protobuf.SingleFieldBuilder<Cluster.RefreshRate,Cluster.RefreshRate.Builder,Cluster.RefreshRateOrBuilder> dnsFailureRefreshRateBuilder_
-
respectDnsTtl_
private boolean respectDnsTtl_
-
dnsLookupFamily_
private int dnsLookupFamily_
-
dnsResolvers_
private java.util.List<Address> dnsResolvers_
-
dnsResolversBuilder_
private com.google.protobuf.RepeatedFieldBuilder<Address,Address.Builder,AddressOrBuilder> dnsResolversBuilder_
-
useTcpForDnsLookups_
private boolean useTcpForDnsLookups_
-
dnsResolutionConfig_
private DnsResolutionConfig dnsResolutionConfig_
-
dnsResolutionConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<DnsResolutionConfig,DnsResolutionConfig.Builder,DnsResolutionConfigOrBuilder> dnsResolutionConfigBuilder_
-
typedDnsResolverConfig_
private TypedExtensionConfig typedDnsResolverConfig_
-
typedDnsResolverConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder,TypedExtensionConfigOrBuilder> typedDnsResolverConfigBuilder_
-
waitForWarmOnInit_
private com.google.protobuf.BoolValue waitForWarmOnInit_
-
waitForWarmOnInitBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder,com.google.protobuf.BoolValueOrBuilder> waitForWarmOnInitBuilder_
-
outlierDetection_
private OutlierDetection outlierDetection_
-
outlierDetectionBuilder_
private com.google.protobuf.SingleFieldBuilder<OutlierDetection,OutlierDetection.Builder,OutlierDetectionOrBuilder> outlierDetectionBuilder_
-
cleanupInterval_
private com.google.protobuf.Duration cleanupInterval_
-
cleanupIntervalBuilder_
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder,com.google.protobuf.DurationOrBuilder> cleanupIntervalBuilder_
-
upstreamBindConfig_
private BindConfig upstreamBindConfig_
-
upstreamBindConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<BindConfig,BindConfig.Builder,BindConfigOrBuilder> upstreamBindConfigBuilder_
-
lbSubsetConfig_
private Cluster.LbSubsetConfig lbSubsetConfig_
-
lbSubsetConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<Cluster.LbSubsetConfig,Cluster.LbSubsetConfig.Builder,Cluster.LbSubsetConfigOrBuilder> lbSubsetConfigBuilder_
-
ringHashLbConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<Cluster.RingHashLbConfig,Cluster.RingHashLbConfig.Builder,Cluster.RingHashLbConfigOrBuilder> ringHashLbConfigBuilder_
-
maglevLbConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<Cluster.MaglevLbConfig,Cluster.MaglevLbConfig.Builder,Cluster.MaglevLbConfigOrBuilder> maglevLbConfigBuilder_
-
originalDstLbConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<Cluster.OriginalDstLbConfig,Cluster.OriginalDstLbConfig.Builder,Cluster.OriginalDstLbConfigOrBuilder> originalDstLbConfigBuilder_
-
leastRequestLbConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<Cluster.LeastRequestLbConfig,Cluster.LeastRequestLbConfig.Builder,Cluster.LeastRequestLbConfigOrBuilder> leastRequestLbConfigBuilder_
-
roundRobinLbConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<Cluster.RoundRobinLbConfig,Cluster.RoundRobinLbConfig.Builder,Cluster.RoundRobinLbConfigOrBuilder> roundRobinLbConfigBuilder_
-
commonLbConfig_
private Cluster.CommonLbConfig commonLbConfig_
-
commonLbConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<Cluster.CommonLbConfig,Cluster.CommonLbConfig.Builder,Cluster.CommonLbConfigOrBuilder> commonLbConfigBuilder_
-
transportSocket_
private TransportSocket transportSocket_
-
transportSocketBuilder_
private com.google.protobuf.SingleFieldBuilder<TransportSocket,TransportSocket.Builder,TransportSocketOrBuilder> transportSocketBuilder_
-
metadata_
private Metadata metadata_
-
metadataBuilder_
private com.google.protobuf.SingleFieldBuilder<Metadata,Metadata.Builder,MetadataOrBuilder> metadataBuilder_
-
protocolSelection_
private int protocolSelection_
-
upstreamConnectionOptions_
private UpstreamConnectionOptions upstreamConnectionOptions_
-
upstreamConnectionOptionsBuilder_
private com.google.protobuf.SingleFieldBuilder<UpstreamConnectionOptions,UpstreamConnectionOptions.Builder,UpstreamConnectionOptionsOrBuilder> upstreamConnectionOptionsBuilder_
-
closeConnectionsOnHostHealthFailure_
private boolean closeConnectionsOnHostHealthFailure_
-
ignoreHealthOnHostRemoval_
private boolean ignoreHealthOnHostRemoval_
-
filters_
private java.util.List<Filter> filters_
-
filtersBuilder_
private com.google.protobuf.RepeatedFieldBuilder<Filter,Filter.Builder,FilterOrBuilder> filtersBuilder_
-
loadBalancingPolicy_
private LoadBalancingPolicy loadBalancingPolicy_
-
loadBalancingPolicyBuilder_
private com.google.protobuf.SingleFieldBuilder<LoadBalancingPolicy,LoadBalancingPolicy.Builder,LoadBalancingPolicyOrBuilder> loadBalancingPolicyBuilder_
-
lrsServer_
private ConfigSource lrsServer_
-
lrsServerBuilder_
private com.google.protobuf.SingleFieldBuilder<ConfigSource,ConfigSource.Builder,ConfigSourceOrBuilder> lrsServerBuilder_
-
trackTimeoutBudgets_
private boolean trackTimeoutBudgets_
-
upstreamConfig_
private TypedExtensionConfig upstreamConfig_
-
upstreamConfigBuilder_
private com.google.protobuf.SingleFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder,TypedExtensionConfigOrBuilder> upstreamConfigBuilder_
-
trackClusterStats_
private TrackClusterStats trackClusterStats_
-
trackClusterStatsBuilder_
private com.google.protobuf.SingleFieldBuilder<TrackClusterStats,TrackClusterStats.Builder,TrackClusterStatsOrBuilder> trackClusterStatsBuilder_
-
preconnectPolicy_
private Cluster.PreconnectPolicy preconnectPolicy_
-
preconnectPolicyBuilder_
private com.google.protobuf.SingleFieldBuilder<Cluster.PreconnectPolicy,Cluster.PreconnectPolicy.Builder,Cluster.PreconnectPolicyOrBuilder> preconnectPolicyBuilder_
-
connectionPoolPerDownstreamConnection_
private boolean connectionPoolPerDownstreamConnection_
-
-
Method Detail
-
getDescriptor
public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
-
internalGetMapFieldReflection
protected com.google.protobuf.MapFieldReflectionAccessor internalGetMapFieldReflection(int number)
- Overrides:
internalGetMapFieldReflection
in classcom.google.protobuf.GeneratedMessage.Builder<Cluster.Builder>
-
internalGetMutableMapFieldReflection
protected com.google.protobuf.MapFieldReflectionAccessor internalGetMutableMapFieldReflection(int number)
- Overrides:
internalGetMutableMapFieldReflection
in classcom.google.protobuf.GeneratedMessage.Builder<Cluster.Builder>
-
internalGetFieldAccessorTable
protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
- Specified by:
internalGetFieldAccessorTable
in classcom.google.protobuf.GeneratedMessage.Builder<Cluster.Builder>
-
maybeForceBuilderInitialization
private void maybeForceBuilderInitialization()
-
clear
public Cluster.Builder clear()
- Specified by:
clear
in interfacecom.google.protobuf.Message.Builder
- Specified by:
clear
in interfacecom.google.protobuf.MessageLite.Builder
- Overrides:
clear
in classcom.google.protobuf.GeneratedMessage.Builder<Cluster.Builder>
-
getDescriptorForType
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
- Specified by:
getDescriptorForType
in interfacecom.google.protobuf.Message.Builder
- Specified by:
getDescriptorForType
in interfacecom.google.protobuf.MessageOrBuilder
- Overrides:
getDescriptorForType
in classcom.google.protobuf.GeneratedMessage.Builder<Cluster.Builder>
-
getDefaultInstanceForType
public Cluster getDefaultInstanceForType()
- Specified by:
getDefaultInstanceForType
in interfacecom.google.protobuf.MessageLiteOrBuilder
- Specified by:
getDefaultInstanceForType
in interfacecom.google.protobuf.MessageOrBuilder
-
build
public Cluster build()
- Specified by:
build
in interfacecom.google.protobuf.Message.Builder
- Specified by:
build
in interfacecom.google.protobuf.MessageLite.Builder
-
buildPartial
public Cluster buildPartial()
- Specified by:
buildPartial
in interfacecom.google.protobuf.Message.Builder
- Specified by:
buildPartial
in interfacecom.google.protobuf.MessageLite.Builder
-
buildPartialRepeatedFields
private void buildPartialRepeatedFields(Cluster result)
-
buildPartial0
private void buildPartial0(Cluster result)
-
buildPartial1
private void buildPartial1(Cluster result)
-
buildPartialOneofs
private void buildPartialOneofs(Cluster result)
-
mergeFrom
public Cluster.Builder mergeFrom(com.google.protobuf.Message other)
- Specified by:
mergeFrom
in interfacecom.google.protobuf.Message.Builder
- Overrides:
mergeFrom
in classcom.google.protobuf.AbstractMessage.Builder<Cluster.Builder>
-
mergeFrom
public Cluster.Builder mergeFrom(Cluster other)
-
isInitialized
public final boolean isInitialized()
- Specified by:
isInitialized
in interfacecom.google.protobuf.MessageLiteOrBuilder
- Overrides:
isInitialized
in classcom.google.protobuf.GeneratedMessage.Builder<Cluster.Builder>
-
mergeFrom
public Cluster.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws java.io.IOException
- Specified by:
mergeFrom
in interfacecom.google.protobuf.Message.Builder
- Specified by:
mergeFrom
in interfacecom.google.protobuf.MessageLite.Builder
- Overrides:
mergeFrom
in classcom.google.protobuf.AbstractMessage.Builder<Cluster.Builder>
- Throws:
java.io.IOException
-
getClusterDiscoveryTypeCase
public Cluster.ClusterDiscoveryTypeCase getClusterDiscoveryTypeCase()
- Specified by:
getClusterDiscoveryTypeCase
in interfaceClusterOrBuilder
-
clearClusterDiscoveryType
public Cluster.Builder clearClusterDiscoveryType()
-
getLbConfigCase
public Cluster.LbConfigCase getLbConfigCase()
- Specified by:
getLbConfigCase
in interfaceClusterOrBuilder
-
clearLbConfig
public Cluster.Builder clearLbConfig()
-
ensureTransportSocketMatchesIsMutable
private void ensureTransportSocketMatchesIsMutable()
-
getTransportSocketMatchesList
public java.util.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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
- Specified by:
getTransportSocketMatchesList
in interfaceClusterOrBuilder
-
getTransportSocketMatchesCount
public int getTransportSocketMatchesCount()
Configuration to use different transport sockets for different endpoints. The entry of ``envoy.transport_socket_match`` in the :ref:`LbEndpoint.Metadata <envoy_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
- Specified by:
getTransportSocketMatchesCount
in interfaceClusterOrBuilder
-
getTransportSocketMatches
public 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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
- Specified by:
getTransportSocketMatches
in interfaceClusterOrBuilder
-
setTransportSocketMatches
public 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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
-
setTransportSocketMatches
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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
-
addTransportSocketMatches
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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
-
addTransportSocketMatches
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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
-
addTransportSocketMatches
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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
-
addTransportSocketMatches
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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
-
addAllTransportSocketMatches
public Cluster.Builder addAllTransportSocketMatches(java.lang.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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
-
clearTransportSocketMatches
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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
-
removeTransportSocketMatches
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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
-
getTransportSocketMatchesBuilder
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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
-
getTransportSocketMatchesOrBuilder
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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
- Specified by:
getTransportSocketMatchesOrBuilder
in interfaceClusterOrBuilder
-
getTransportSocketMatchesOrBuilderList
public java.util.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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
- Specified by:
getTransportSocketMatchesOrBuilderList
in interfaceClusterOrBuilder
-
addTransportSocketMatchesBuilder
public 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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
-
addTransportSocketMatchesBuilder
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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
-
getTransportSocketMatchesBuilderList
public java.util.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_v3_api_field_config.endpoint.v3.LbEndpoint.metadata>` is used to match against the transport sockets as they appear in the list. If a match is not found, the search continues in :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`. The first :ref:`match <envoy_v3_api_msg_config.cluster.v3.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_v3_api_msg_config.cluster.v3.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``, the locality metadata is then checked for a match. Barring any matches in the endpoint or locality metadata, the 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_v3_api_field_config.core.v3.HealthCheck.transport_socket_match_criteria>` field. [#comment:TODO(incfly): add a detailed architecture doc on intended usage.]
repeated .envoy.config.cluster.v3.Cluster.TransportSocketMatch transport_socket_matches = 43;
-
getTransportSocketMatchesFieldBuilder
private com.google.protobuf.RepeatedFieldBuilder<Cluster.TransportSocketMatch,Cluster.TransportSocketMatch.Builder,Cluster.TransportSocketMatchOrBuilder> getTransportSocketMatchesFieldBuilder()
-
getName
public java.lang.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_v3_api_field_config.cluster.v3.Cluster.alt_stat_name>` is not provided. Any ``:`` in the cluster name will be converted to ``_`` when emitting statistics.
string name = 1 [(.validate.rules) = { ... }
- Specified by:
getName
in interfaceClusterOrBuilder
- Returns:
- The name.
-
getNameBytes
public 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_v3_api_field_config.cluster.v3.Cluster.alt_stat_name>` is not provided. Any ``:`` in the cluster name will be converted to ``_`` when emitting statistics.
string name = 1 [(.validate.rules) = { ... }
- Specified by:
getNameBytes
in interfaceClusterOrBuilder
- Returns:
- The bytes for name.
-
setName
public Cluster.Builder setName(java.lang.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_v3_api_field_config.cluster.v3.Cluster.alt_stat_name>` is not provided. Any ``:`` in the cluster name will be converted to ``_`` when emitting statistics.
string name = 1 [(.validate.rules) = { ... }
- Parameters:
value
- The name to set.- Returns:
- This builder for chaining.
-
clearName
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_v3_api_field_config.cluster.v3.Cluster.alt_stat_name>` is not provided. Any ``:`` in the cluster name will be converted to ``_`` when emitting statistics.
string name = 1 [(.validate.rules) = { ... }
- Returns:
- This builder for chaining.
-
setNameBytes
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_v3_api_field_config.cluster.v3.Cluster.alt_stat_name>` is not provided. Any ``:`` in the cluster name will be converted to ``_`` when emitting statistics.
string name = 1 [(.validate.rules) = { ... }
- Parameters:
value
- The bytes for name to set.- Returns:
- This builder for chaining.
-
getAltStatName
public java.lang.String getAltStatName()
An optional alternative to the cluster name to be used for observability. This name is used emitting stats for the cluster and access logging the cluster name. This will appear as additional information in configuration dumps of a cluster's current status as :ref:`observability_name <envoy_v3_api_field_admin.v3.ClusterStatus.observability_name>` and as an additional tag "upstream_cluster.name" while tracing. Note: 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 [(.udpa.annotations.field_migrate) = { ... }
- Specified by:
getAltStatName
in interfaceClusterOrBuilder
- Returns:
- The altStatName.
-
getAltStatNameBytes
public com.google.protobuf.ByteString getAltStatNameBytes()
An optional alternative to the cluster name to be used for observability. This name is used emitting stats for the cluster and access logging the cluster name. This will appear as additional information in configuration dumps of a cluster's current status as :ref:`observability_name <envoy_v3_api_field_admin.v3.ClusterStatus.observability_name>` and as an additional tag "upstream_cluster.name" while tracing. Note: 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 [(.udpa.annotations.field_migrate) = { ... }
- Specified by:
getAltStatNameBytes
in interfaceClusterOrBuilder
- Returns:
- The bytes for altStatName.
-
setAltStatName
public Cluster.Builder setAltStatName(java.lang.String value)
An optional alternative to the cluster name to be used for observability. This name is used emitting stats for the cluster and access logging the cluster name. This will appear as additional information in configuration dumps of a cluster's current status as :ref:`observability_name <envoy_v3_api_field_admin.v3.ClusterStatus.observability_name>` and as an additional tag "upstream_cluster.name" while tracing. Note: 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 [(.udpa.annotations.field_migrate) = { ... }
- Parameters:
value
- The altStatName to set.- Returns:
- This builder for chaining.
-
clearAltStatName
public Cluster.Builder clearAltStatName()
An optional alternative to the cluster name to be used for observability. This name is used emitting stats for the cluster and access logging the cluster name. This will appear as additional information in configuration dumps of a cluster's current status as :ref:`observability_name <envoy_v3_api_field_admin.v3.ClusterStatus.observability_name>` and as an additional tag "upstream_cluster.name" while tracing. Note: 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 [(.udpa.annotations.field_migrate) = { ... }
- Returns:
- This builder for chaining.
-
setAltStatNameBytes
public Cluster.Builder setAltStatNameBytes(com.google.protobuf.ByteString value)
An optional alternative to the cluster name to be used for observability. This name is used emitting stats for the cluster and access logging the cluster name. This will appear as additional information in configuration dumps of a cluster's current status as :ref:`observability_name <envoy_v3_api_field_admin.v3.ClusterStatus.observability_name>` and as an additional tag "upstream_cluster.name" while tracing. Note: 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 [(.udpa.annotations.field_migrate) = { ... }
- Parameters:
value
- The bytes for altStatName to set.- Returns:
- This builder for chaining.
-
hasType
public boolean hasType()
The :ref:`service discovery type <arch_overview_service_discovery_types>` to use for resolving the cluster.
.envoy.config.cluster.v3.Cluster.DiscoveryType type = 2 [(.validate.rules) = { ... }
- Specified by:
hasType
in interfaceClusterOrBuilder
- Returns:
- Whether the type field is set.
-
getTypeValue
public int getTypeValue()
The :ref:`service discovery type <arch_overview_service_discovery_types>` to use for resolving the cluster.
.envoy.config.cluster.v3.Cluster.DiscoveryType type = 2 [(.validate.rules) = { ... }
- Specified by:
getTypeValue
in interfaceClusterOrBuilder
- Returns:
- The enum numeric value on the wire for type.
-
setTypeValue
public Cluster.Builder setTypeValue(int value)
The :ref:`service discovery type <arch_overview_service_discovery_types>` to use for resolving the cluster.
.envoy.config.cluster.v3.Cluster.DiscoveryType type = 2 [(.validate.rules) = { ... }
- Parameters:
value
- The enum numeric value on the wire for type to set.- Returns:
- This builder for chaining.
-
getType
public Cluster.DiscoveryType getType()
The :ref:`service discovery type <arch_overview_service_discovery_types>` to use for resolving the cluster.
.envoy.config.cluster.v3.Cluster.DiscoveryType type = 2 [(.validate.rules) = { ... }
- Specified by:
getType
in interfaceClusterOrBuilder
- Returns:
- The type.
-
setType
public 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.v3.Cluster.DiscoveryType type = 2 [(.validate.rules) = { ... }
- Parameters:
value
- The type to set.- Returns:
- This builder for chaining.
-
clearType
public Cluster.Builder clearType()
The :ref:`service discovery type <arch_overview_service_discovery_types>` to use for resolving the cluster.
.envoy.config.cluster.v3.Cluster.DiscoveryType type = 2 [(.validate.rules) = { ... }
- Returns:
- This builder for chaining.
-
hasClusterType
public boolean hasClusterType()
The custom cluster type.
.envoy.config.cluster.v3.Cluster.CustomClusterType cluster_type = 38;
- Specified by:
hasClusterType
in interfaceClusterOrBuilder
- Returns:
- Whether the clusterType field is set.
-
getClusterType
public Cluster.CustomClusterType getClusterType()
The custom cluster type.
.envoy.config.cluster.v3.Cluster.CustomClusterType cluster_type = 38;
- Specified by:
getClusterType
in interfaceClusterOrBuilder
- Returns:
- The clusterType.
-
setClusterType
public Cluster.Builder setClusterType(Cluster.CustomClusterType value)
The custom cluster type.
.envoy.config.cluster.v3.Cluster.CustomClusterType cluster_type = 38;
-
setClusterType
public Cluster.Builder setClusterType(Cluster.CustomClusterType.Builder builderForValue)
The custom cluster type.
.envoy.config.cluster.v3.Cluster.CustomClusterType cluster_type = 38;
-
mergeClusterType
public Cluster.Builder mergeClusterType(Cluster.CustomClusterType value)
The custom cluster type.
.envoy.config.cluster.v3.Cluster.CustomClusterType cluster_type = 38;
-
clearClusterType
public Cluster.Builder clearClusterType()
The custom cluster type.
.envoy.config.cluster.v3.Cluster.CustomClusterType cluster_type = 38;
-
getClusterTypeBuilder
public Cluster.CustomClusterType.Builder getClusterTypeBuilder()
The custom cluster type.
.envoy.config.cluster.v3.Cluster.CustomClusterType cluster_type = 38;
-
getClusterTypeOrBuilder
public Cluster.CustomClusterTypeOrBuilder getClusterTypeOrBuilder()
The custom cluster type.
.envoy.config.cluster.v3.Cluster.CustomClusterType cluster_type = 38;
- Specified by:
getClusterTypeOrBuilder
in interfaceClusterOrBuilder
-
getClusterTypeFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Cluster.CustomClusterType,Cluster.CustomClusterType.Builder,Cluster.CustomClusterTypeOrBuilder> getClusterTypeFieldBuilder()
The custom cluster type.
.envoy.config.cluster.v3.Cluster.CustomClusterType cluster_type = 38;
-
hasEdsClusterConfig
public boolean hasEdsClusterConfig()
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v3.Cluster.EdsClusterConfig eds_cluster_config = 3;
- Specified by:
hasEdsClusterConfig
in interfaceClusterOrBuilder
- Returns:
- Whether the edsClusterConfig field is set.
-
getEdsClusterConfig
public Cluster.EdsClusterConfig getEdsClusterConfig()
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v3.Cluster.EdsClusterConfig eds_cluster_config = 3;
- Specified by:
getEdsClusterConfig
in interfaceClusterOrBuilder
- Returns:
- The edsClusterConfig.
-
setEdsClusterConfig
public Cluster.Builder setEdsClusterConfig(Cluster.EdsClusterConfig value)
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v3.Cluster.EdsClusterConfig eds_cluster_config = 3;
-
setEdsClusterConfig
public Cluster.Builder setEdsClusterConfig(Cluster.EdsClusterConfig.Builder builderForValue)
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v3.Cluster.EdsClusterConfig eds_cluster_config = 3;
-
mergeEdsClusterConfig
public Cluster.Builder mergeEdsClusterConfig(Cluster.EdsClusterConfig value)
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v3.Cluster.EdsClusterConfig eds_cluster_config = 3;
-
clearEdsClusterConfig
public Cluster.Builder clearEdsClusterConfig()
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v3.Cluster.EdsClusterConfig eds_cluster_config = 3;
-
getEdsClusterConfigBuilder
public Cluster.EdsClusterConfig.Builder getEdsClusterConfigBuilder()
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v3.Cluster.EdsClusterConfig eds_cluster_config = 3;
-
getEdsClusterConfigOrBuilder
public Cluster.EdsClusterConfigOrBuilder getEdsClusterConfigOrBuilder()
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v3.Cluster.EdsClusterConfig eds_cluster_config = 3;
- Specified by:
getEdsClusterConfigOrBuilder
in interfaceClusterOrBuilder
-
getEdsClusterConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Cluster.EdsClusterConfig,Cluster.EdsClusterConfig.Builder,Cluster.EdsClusterConfigOrBuilder> getEdsClusterConfigFieldBuilder()
Configuration to use for EDS updates for the Cluster.
.envoy.config.cluster.v3.Cluster.EdsClusterConfig eds_cluster_config = 3;
-
hasConnectTimeout
public boolean hasConnectTimeout()
The timeout for new network connections to hosts in the cluster. If not set, a default value of 5s will be used.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }
- Specified by:
hasConnectTimeout
in interfaceClusterOrBuilder
- Returns:
- Whether the connectTimeout field is set.
-
getConnectTimeout
public com.google.protobuf.Duration getConnectTimeout()
The timeout for new network connections to hosts in the cluster. If not set, a default value of 5s will be used.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }
- Specified by:
getConnectTimeout
in interfaceClusterOrBuilder
- Returns:
- The connectTimeout.
-
setConnectTimeout
public Cluster.Builder setConnectTimeout(com.google.protobuf.Duration value)
The timeout for new network connections to hosts in the cluster. If not set, a default value of 5s will be used.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }
-
setConnectTimeout
public Cluster.Builder setConnectTimeout(com.google.protobuf.Duration.Builder builderForValue)
The timeout for new network connections to hosts in the cluster. If not set, a default value of 5s will be used.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }
-
mergeConnectTimeout
public Cluster.Builder mergeConnectTimeout(com.google.protobuf.Duration value)
The timeout for new network connections to hosts in the cluster. If not set, a default value of 5s will be used.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }
-
clearConnectTimeout
public Cluster.Builder clearConnectTimeout()
The timeout for new network connections to hosts in the cluster. If not set, a default value of 5s will be used.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }
-
getConnectTimeoutBuilder
public com.google.protobuf.Duration.Builder getConnectTimeoutBuilder()
The timeout for new network connections to hosts in the cluster. If not set, a default value of 5s will be used.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }
-
getConnectTimeoutOrBuilder
public com.google.protobuf.DurationOrBuilder getConnectTimeoutOrBuilder()
The timeout for new network connections to hosts in the cluster. If not set, a default value of 5s will be used.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }
- Specified by:
getConnectTimeoutOrBuilder
in interfaceClusterOrBuilder
-
getConnectTimeoutFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder,com.google.protobuf.DurationOrBuilder> getConnectTimeoutFieldBuilder()
The timeout for new network connections to hosts in the cluster. If not set, a default value of 5s will be used.
.google.protobuf.Duration connect_timeout = 4 [(.validate.rules) = { ... }
-
hasPerConnectionBufferLimitBytes
public 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) = { ... }
- Specified by:
hasPerConnectionBufferLimitBytes
in interfaceClusterOrBuilder
- Returns:
- Whether the perConnectionBufferLimitBytes field is set.
-
getPerConnectionBufferLimitBytes
public 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) = { ... }
- Specified by:
getPerConnectionBufferLimitBytes
in interfaceClusterOrBuilder
- Returns:
- The perConnectionBufferLimitBytes.
-
setPerConnectionBufferLimitBytes
public 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) = { ... }
-
setPerConnectionBufferLimitBytes
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) = { ... }
-
mergePerConnectionBufferLimitBytes
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) = { ... }
-
clearPerConnectionBufferLimitBytes
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) = { ... }
-
getPerConnectionBufferLimitBytesBuilder
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) = { ... }
-
getPerConnectionBufferLimitBytesOrBuilder
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) = { ... }
- Specified by:
getPerConnectionBufferLimitBytesOrBuilder
in interfaceClusterOrBuilder
-
getPerConnectionBufferLimitBytesFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,com.google.protobuf.UInt32Value.Builder,com.google.protobuf.UInt32ValueOrBuilder> getPerConnectionBufferLimitBytesFieldBuilder()
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) = { ... }
-
getLbPolicyValue
public int getLbPolicyValue()
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use when picking a host in the cluster.
.envoy.config.cluster.v3.Cluster.LbPolicy lb_policy = 6 [(.validate.rules) = { ... }
- Specified by:
getLbPolicyValue
in interfaceClusterOrBuilder
- Returns:
- The enum numeric value on the wire for lbPolicy.
-
setLbPolicyValue
public Cluster.Builder setLbPolicyValue(int value)
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use when picking a host in the cluster.
.envoy.config.cluster.v3.Cluster.LbPolicy lb_policy = 6 [(.validate.rules) = { ... }
- Parameters:
value
- The enum numeric value on the wire for lbPolicy to set.- Returns:
- This builder for chaining.
-
getLbPolicy
public Cluster.LbPolicy getLbPolicy()
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use when picking a host in the cluster.
.envoy.config.cluster.v3.Cluster.LbPolicy lb_policy = 6 [(.validate.rules) = { ... }
- Specified by:
getLbPolicy
in interfaceClusterOrBuilder
- Returns:
- The lbPolicy.
-
setLbPolicy
public 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.
.envoy.config.cluster.v3.Cluster.LbPolicy lb_policy = 6 [(.validate.rules) = { ... }
- Parameters:
value
- The lbPolicy to set.- Returns:
- This builder for chaining.
-
clearLbPolicy
public Cluster.Builder clearLbPolicy()
The :ref:`load balancer type <arch_overview_load_balancing_types>` to use when picking a host in the cluster.
.envoy.config.cluster.v3.Cluster.LbPolicy lb_policy = 6 [(.validate.rules) = { ... }
- Returns:
- This builder for chaining.
-
hasLoadAssignment
public boolean hasLoadAssignment()
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;
- Specified by:
hasLoadAssignment
in interfaceClusterOrBuilder
- Returns:
- Whether the loadAssignment field is set.
-
getLoadAssignment
public ClusterLoadAssignment getLoadAssignment()
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;
- Specified by:
getLoadAssignment
in interfaceClusterOrBuilder
- Returns:
- The loadAssignment.
-
setLoadAssignment
public Cluster.Builder setLoadAssignment(ClusterLoadAssignment value)
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;
-
setLoadAssignment
public Cluster.Builder setLoadAssignment(ClusterLoadAssignment.Builder builderForValue)
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;
-
mergeLoadAssignment
public Cluster.Builder mergeLoadAssignment(ClusterLoadAssignment value)
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;
-
clearLoadAssignment
public Cluster.Builder clearLoadAssignment()
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;
-
getLoadAssignmentBuilder
public ClusterLoadAssignment.Builder getLoadAssignmentBuilder()
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;
-
getLoadAssignmentOrBuilder
public ClusterLoadAssignmentOrBuilder getLoadAssignmentOrBuilder()
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;
- Specified by:
getLoadAssignmentOrBuilder
in interfaceClusterOrBuilder
-
getLoadAssignmentFieldBuilder
private com.google.protobuf.SingleFieldBuilder<ClusterLoadAssignment,ClusterLoadAssignment.Builder,ClusterLoadAssignmentOrBuilder> getLoadAssignmentFieldBuilder()
Setting this is required for specifying members of :ref:`STATIC<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STATIC>`, :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_msg_config.endpoint.v3.ClusterLoadAssignment>`.
.envoy.config.endpoint.v3.ClusterLoadAssignment load_assignment = 33;
-
ensureHealthChecksIsMutable
private void ensureHealthChecksIsMutable()
-
getHealthChecksList
public java.util.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.v3.HealthCheck health_checks = 8;
- Specified by:
getHealthChecksList
in interfaceClusterOrBuilder
-
getHealthChecksCount
public 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.v3.HealthCheck health_checks = 8;
- Specified by:
getHealthChecksCount
in interfaceClusterOrBuilder
-
getHealthChecks
public 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.v3.HealthCheck health_checks = 8;
- Specified by:
getHealthChecks
in interfaceClusterOrBuilder
-
setHealthChecks
public 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.v3.HealthCheck health_checks = 8;
-
setHealthChecks
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.v3.HealthCheck health_checks = 8;
-
addHealthChecks
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.v3.HealthCheck health_checks = 8;
-
addHealthChecks
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.v3.HealthCheck health_checks = 8;
-
addHealthChecks
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.v3.HealthCheck health_checks = 8;
-
addHealthChecks
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.v3.HealthCheck health_checks = 8;
-
addAllHealthChecks
public Cluster.Builder addAllHealthChecks(java.lang.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.v3.HealthCheck health_checks = 8;
-
clearHealthChecks
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.v3.HealthCheck health_checks = 8;
-
removeHealthChecks
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.v3.HealthCheck health_checks = 8;
-
getHealthChecksBuilder
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.v3.HealthCheck health_checks = 8;
-
getHealthChecksOrBuilder
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.v3.HealthCheck health_checks = 8;
- Specified by:
getHealthChecksOrBuilder
in interfaceClusterOrBuilder
-
getHealthChecksOrBuilderList
public java.util.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.v3.HealthCheck health_checks = 8;
- Specified by:
getHealthChecksOrBuilderList
in interfaceClusterOrBuilder
-
addHealthChecksBuilder
public 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.v3.HealthCheck health_checks = 8;
-
addHealthChecksBuilder
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.v3.HealthCheck health_checks = 8;
-
getHealthChecksBuilderList
public java.util.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.v3.HealthCheck health_checks = 8;
-
getHealthChecksFieldBuilder
private com.google.protobuf.RepeatedFieldBuilder<HealthCheck,HealthCheck.Builder,HealthCheckOrBuilder> getHealthChecksFieldBuilder()
-
hasMaxRequestsPerConnection
@Deprecated public boolean hasMaxRequestsPerConnection()
Deprecated.envoy.config.cluster.v3.Cluster.max_requests_per_connection is deprecated. See envoy/config/cluster/v3/cluster.proto;l=877Optional 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. .. attention:: This field has been deprecated in favor of the :ref:`max_requests_per_connection <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_requests_per_connection>` field.
.google.protobuf.UInt32Value max_requests_per_connection = 9 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
hasMaxRequestsPerConnection
in interfaceClusterOrBuilder
- Returns:
- Whether the maxRequestsPerConnection field is set.
-
getMaxRequestsPerConnection
@Deprecated public com.google.protobuf.UInt32Value getMaxRequestsPerConnection()
Deprecated.envoy.config.cluster.v3.Cluster.max_requests_per_connection is deprecated. See envoy/config/cluster/v3/cluster.proto;l=877Optional 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. .. attention:: This field has been deprecated in favor of the :ref:`max_requests_per_connection <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_requests_per_connection>` field.
.google.protobuf.UInt32Value max_requests_per_connection = 9 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getMaxRequestsPerConnection
in interfaceClusterOrBuilder
- Returns:
- The maxRequestsPerConnection.
-
setMaxRequestsPerConnection
@Deprecated public Cluster.Builder setMaxRequestsPerConnection(com.google.protobuf.UInt32Value value)
Deprecated.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. .. attention:: This field has been deprecated in favor of the :ref:`max_requests_per_connection <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_requests_per_connection>` field.
.google.protobuf.UInt32Value max_requests_per_connection = 9 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
setMaxRequestsPerConnection
@Deprecated public Cluster.Builder setMaxRequestsPerConnection(com.google.protobuf.UInt32Value.Builder builderForValue)
Deprecated.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. .. attention:: This field has been deprecated in favor of the :ref:`max_requests_per_connection <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_requests_per_connection>` field.
.google.protobuf.UInt32Value max_requests_per_connection = 9 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
mergeMaxRequestsPerConnection
@Deprecated public Cluster.Builder mergeMaxRequestsPerConnection(com.google.protobuf.UInt32Value value)
Deprecated.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. .. attention:: This field has been deprecated in favor of the :ref:`max_requests_per_connection <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_requests_per_connection>` field.
.google.protobuf.UInt32Value max_requests_per_connection = 9 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
clearMaxRequestsPerConnection
@Deprecated public Cluster.Builder clearMaxRequestsPerConnection()
Deprecated.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. .. attention:: This field has been deprecated in favor of the :ref:`max_requests_per_connection <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_requests_per_connection>` field.
.google.protobuf.UInt32Value max_requests_per_connection = 9 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getMaxRequestsPerConnectionBuilder
@Deprecated public com.google.protobuf.UInt32Value.Builder getMaxRequestsPerConnectionBuilder()
Deprecated.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. .. attention:: This field has been deprecated in favor of the :ref:`max_requests_per_connection <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_requests_per_connection>` field.
.google.protobuf.UInt32Value max_requests_per_connection = 9 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getMaxRequestsPerConnectionOrBuilder
@Deprecated public com.google.protobuf.UInt32ValueOrBuilder getMaxRequestsPerConnectionOrBuilder()
Deprecated.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. .. attention:: This field has been deprecated in favor of the :ref:`max_requests_per_connection <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_requests_per_connection>` field.
.google.protobuf.UInt32Value max_requests_per_connection = 9 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getMaxRequestsPerConnectionOrBuilder
in interfaceClusterOrBuilder
-
getMaxRequestsPerConnectionFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.UInt32Value,com.google.protobuf.UInt32Value.Builder,com.google.protobuf.UInt32ValueOrBuilder> getMaxRequestsPerConnectionFieldBuilder()
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. .. attention:: This field has been deprecated in favor of the :ref:`max_requests_per_connection <envoy_v3_api_field_config.core.v3.HttpProtocolOptions.max_requests_per_connection>` field.
.google.protobuf.UInt32Value max_requests_per_connection = 9 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
hasCircuitBreakers
public boolean hasCircuitBreakers()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v3.CircuitBreakers circuit_breakers = 10;
- Specified by:
hasCircuitBreakers
in interfaceClusterOrBuilder
- Returns:
- Whether the circuitBreakers field is set.
-
getCircuitBreakers
public CircuitBreakers getCircuitBreakers()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v3.CircuitBreakers circuit_breakers = 10;
- Specified by:
getCircuitBreakers
in interfaceClusterOrBuilder
- Returns:
- The circuitBreakers.
-
setCircuitBreakers
public Cluster.Builder setCircuitBreakers(CircuitBreakers value)
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v3.CircuitBreakers circuit_breakers = 10;
-
setCircuitBreakers
public Cluster.Builder setCircuitBreakers(CircuitBreakers.Builder builderForValue)
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v3.CircuitBreakers circuit_breakers = 10;
-
mergeCircuitBreakers
public Cluster.Builder mergeCircuitBreakers(CircuitBreakers value)
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v3.CircuitBreakers circuit_breakers = 10;
-
clearCircuitBreakers
public Cluster.Builder clearCircuitBreakers()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v3.CircuitBreakers circuit_breakers = 10;
-
getCircuitBreakersBuilder
public CircuitBreakers.Builder getCircuitBreakersBuilder()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v3.CircuitBreakers circuit_breakers = 10;
-
getCircuitBreakersOrBuilder
public CircuitBreakersOrBuilder getCircuitBreakersOrBuilder()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v3.CircuitBreakers circuit_breakers = 10;
- Specified by:
getCircuitBreakersOrBuilder
in interfaceClusterOrBuilder
-
getCircuitBreakersFieldBuilder
private com.google.protobuf.SingleFieldBuilder<CircuitBreakers,CircuitBreakers.Builder,CircuitBreakersOrBuilder> getCircuitBreakersFieldBuilder()
Optional :ref:`circuit breaking <arch_overview_circuit_break>` for the cluster.
.envoy.config.cluster.v3.CircuitBreakers circuit_breakers = 10;
-
hasUpstreamHttpProtocolOptions
@Deprecated public boolean hasUpstreamHttpProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.upstream_http_protocol_options is deprecated. See envoy/config/cluster/v3/cluster.proto;l=893HTTP protocol options that are applied only to upstream HTTP connections. These options apply to all HTTP versions. This has been deprecated in favor of :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. upstream_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.UpstreamHttpProtocolOptions upstream_http_protocol_options = 46 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
hasUpstreamHttpProtocolOptions
in interfaceClusterOrBuilder
- Returns:
- Whether the upstreamHttpProtocolOptions field is set.
-
getUpstreamHttpProtocolOptions
@Deprecated public UpstreamHttpProtocolOptions getUpstreamHttpProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.upstream_http_protocol_options is deprecated. See envoy/config/cluster/v3/cluster.proto;l=893HTTP protocol options that are applied only to upstream HTTP connections. These options apply to all HTTP versions. This has been deprecated in favor of :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. upstream_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.UpstreamHttpProtocolOptions upstream_http_protocol_options = 46 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getUpstreamHttpProtocolOptions
in interfaceClusterOrBuilder
- Returns:
- The upstreamHttpProtocolOptions.
-
setUpstreamHttpProtocolOptions
@Deprecated public Cluster.Builder setUpstreamHttpProtocolOptions(UpstreamHttpProtocolOptions value)
Deprecated.HTTP protocol options that are applied only to upstream HTTP connections. These options apply to all HTTP versions. This has been deprecated in favor of :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. upstream_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.UpstreamHttpProtocolOptions upstream_http_protocol_options = 46 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
setUpstreamHttpProtocolOptions
@Deprecated public Cluster.Builder setUpstreamHttpProtocolOptions(UpstreamHttpProtocolOptions.Builder builderForValue)
Deprecated.HTTP protocol options that are applied only to upstream HTTP connections. These options apply to all HTTP versions. This has been deprecated in favor of :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. upstream_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.UpstreamHttpProtocolOptions upstream_http_protocol_options = 46 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
mergeUpstreamHttpProtocolOptions
@Deprecated public Cluster.Builder mergeUpstreamHttpProtocolOptions(UpstreamHttpProtocolOptions value)
Deprecated.HTTP protocol options that are applied only to upstream HTTP connections. These options apply to all HTTP versions. This has been deprecated in favor of :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. upstream_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.UpstreamHttpProtocolOptions upstream_http_protocol_options = 46 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
clearUpstreamHttpProtocolOptions
@Deprecated public Cluster.Builder clearUpstreamHttpProtocolOptions()
Deprecated.HTTP protocol options that are applied only to upstream HTTP connections. These options apply to all HTTP versions. This has been deprecated in favor of :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. upstream_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.UpstreamHttpProtocolOptions upstream_http_protocol_options = 46 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getUpstreamHttpProtocolOptionsBuilder
@Deprecated public UpstreamHttpProtocolOptions.Builder getUpstreamHttpProtocolOptionsBuilder()
Deprecated.HTTP protocol options that are applied only to upstream HTTP connections. These options apply to all HTTP versions. This has been deprecated in favor of :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. upstream_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.UpstreamHttpProtocolOptions upstream_http_protocol_options = 46 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getUpstreamHttpProtocolOptionsOrBuilder
@Deprecated public UpstreamHttpProtocolOptionsOrBuilder getUpstreamHttpProtocolOptionsOrBuilder()
Deprecated.HTTP protocol options that are applied only to upstream HTTP connections. These options apply to all HTTP versions. This has been deprecated in favor of :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. upstream_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.UpstreamHttpProtocolOptions upstream_http_protocol_options = 46 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getUpstreamHttpProtocolOptionsOrBuilder
in interfaceClusterOrBuilder
-
getUpstreamHttpProtocolOptionsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<UpstreamHttpProtocolOptions,UpstreamHttpProtocolOptions.Builder,UpstreamHttpProtocolOptionsOrBuilder> getUpstreamHttpProtocolOptionsFieldBuilder()
HTTP protocol options that are applied only to upstream HTTP connections. These options apply to all HTTP versions. This has been deprecated in favor of :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. upstream_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.UpstreamHttpProtocolOptions upstream_http_protocol_options = 46 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
hasCommonHttpProtocolOptions
@Deprecated public boolean hasCommonHttpProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.common_http_protocol_options is deprecated. See envoy/config/cluster/v3/cluster.proto;l=906Additional options when handling HTTP requests upstream. These options will be applicable to both HTTP1 and HTTP2 requests. This has been deprecated in favor of :ref:`common_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.common_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. common_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 29 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
hasCommonHttpProtocolOptions
in interfaceClusterOrBuilder
- Returns:
- Whether the commonHttpProtocolOptions field is set.
-
getCommonHttpProtocolOptions
@Deprecated public HttpProtocolOptions getCommonHttpProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.common_http_protocol_options is deprecated. See envoy/config/cluster/v3/cluster.proto;l=906Additional options when handling HTTP requests upstream. These options will be applicable to both HTTP1 and HTTP2 requests. This has been deprecated in favor of :ref:`common_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.common_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. common_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 29 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getCommonHttpProtocolOptions
in interfaceClusterOrBuilder
- Returns:
- The commonHttpProtocolOptions.
-
setCommonHttpProtocolOptions
@Deprecated public Cluster.Builder setCommonHttpProtocolOptions(HttpProtocolOptions value)
Deprecated.Additional options when handling HTTP requests upstream. These options will be applicable to both HTTP1 and HTTP2 requests. This has been deprecated in favor of :ref:`common_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.common_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. common_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 29 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
setCommonHttpProtocolOptions
@Deprecated public Cluster.Builder setCommonHttpProtocolOptions(HttpProtocolOptions.Builder builderForValue)
Deprecated.Additional options when handling HTTP requests upstream. These options will be applicable to both HTTP1 and HTTP2 requests. This has been deprecated in favor of :ref:`common_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.common_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. common_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 29 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
mergeCommonHttpProtocolOptions
@Deprecated public Cluster.Builder mergeCommonHttpProtocolOptions(HttpProtocolOptions value)
Deprecated.Additional options when handling HTTP requests upstream. These options will be applicable to both HTTP1 and HTTP2 requests. This has been deprecated in favor of :ref:`common_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.common_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. common_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 29 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
clearCommonHttpProtocolOptions
@Deprecated public Cluster.Builder clearCommonHttpProtocolOptions()
Deprecated.Additional options when handling HTTP requests upstream. These options will be applicable to both HTTP1 and HTTP2 requests. This has been deprecated in favor of :ref:`common_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.common_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. common_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 29 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getCommonHttpProtocolOptionsBuilder
@Deprecated public HttpProtocolOptions.Builder getCommonHttpProtocolOptionsBuilder()
Deprecated.Additional options when handling HTTP requests upstream. These options will be applicable to both HTTP1 and HTTP2 requests. This has been deprecated in favor of :ref:`common_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.common_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. common_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 29 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getCommonHttpProtocolOptionsOrBuilder
@Deprecated public HttpProtocolOptionsOrBuilder getCommonHttpProtocolOptionsOrBuilder()
Deprecated.Additional options when handling HTTP requests upstream. These options will be applicable to both HTTP1 and HTTP2 requests. This has been deprecated in favor of :ref:`common_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.common_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. common_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 29 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getCommonHttpProtocolOptionsOrBuilder
in interfaceClusterOrBuilder
-
getCommonHttpProtocolOptionsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<HttpProtocolOptions,HttpProtocolOptions.Builder,HttpProtocolOptionsOrBuilder> getCommonHttpProtocolOptionsFieldBuilder()
Additional options when handling HTTP requests upstream. These options will be applicable to both HTTP1 and HTTP2 requests. This has been deprecated in favor of :ref:`common_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.common_http_protocol_options>` in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. common_http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.HttpProtocolOptions common_http_protocol_options = 29 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
hasHttpProtocolOptions
@Deprecated public boolean hasHttpProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.http_protocol_options is deprecated. See envoy/config/cluster/v3/cluster.proto;l=917Additional options when handling HTTP1 requests. This has been deprecated in favor of http_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 13 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
hasHttpProtocolOptions
in interfaceClusterOrBuilder
- Returns:
- Whether the httpProtocolOptions field is set.
-
getHttpProtocolOptions
@Deprecated public Http1ProtocolOptions getHttpProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.http_protocol_options is deprecated. See envoy/config/cluster/v3/cluster.proto;l=917Additional options when handling HTTP1 requests. This has been deprecated in favor of http_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 13 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getHttpProtocolOptions
in interfaceClusterOrBuilder
- Returns:
- The httpProtocolOptions.
-
setHttpProtocolOptions
@Deprecated public Cluster.Builder setHttpProtocolOptions(Http1ProtocolOptions value)
Deprecated.Additional options when handling HTTP1 requests. This has been deprecated in favor of http_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 13 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
setHttpProtocolOptions
@Deprecated public Cluster.Builder setHttpProtocolOptions(Http1ProtocolOptions.Builder builderForValue)
Deprecated.Additional options when handling HTTP1 requests. This has been deprecated in favor of http_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 13 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
mergeHttpProtocolOptions
@Deprecated public Cluster.Builder mergeHttpProtocolOptions(Http1ProtocolOptions value)
Deprecated.Additional options when handling HTTP1 requests. This has been deprecated in favor of http_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 13 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
clearHttpProtocolOptions
@Deprecated public Cluster.Builder clearHttpProtocolOptions()
Deprecated.Additional options when handling HTTP1 requests. This has been deprecated in favor of http_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 13 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getHttpProtocolOptionsBuilder
@Deprecated public Http1ProtocolOptions.Builder getHttpProtocolOptionsBuilder()
Deprecated.Additional options when handling HTTP1 requests. This has been deprecated in favor of http_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 13 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getHttpProtocolOptionsOrBuilder
@Deprecated public Http1ProtocolOptionsOrBuilder getHttpProtocolOptionsOrBuilder()
Deprecated.Additional options when handling HTTP1 requests. This has been deprecated in favor of http_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 13 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getHttpProtocolOptionsOrBuilder
in interfaceClusterOrBuilder
-
getHttpProtocolOptionsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Http1ProtocolOptions,Http1ProtocolOptions.Builder,Http1ProtocolOptionsOrBuilder> getHttpProtocolOptionsFieldBuilder()
Additional options when handling HTTP1 requests. This has been deprecated in favor of http_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http1ProtocolOptions http_protocol_options = 13 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
hasHttp2ProtocolOptions
@Deprecated public boolean hasHttp2ProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.http2_protocol_options is deprecated. See envoy/config/cluster/v3/cluster.proto;l=933Even if default HTTP2 protocol options are desired, this field must be set so that Envoy will assume that the upstream supports HTTP/2 when making new HTTP connection pool connections. Currently, Envoy only supports prior knowledge for upstream connections. Even if TLS is used with ALPN, ``http2_protocol_options`` must be specified. As an aside this allows HTTP/2 connections to happen over plain text. This has been deprecated in favor of http2_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http2_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 14 [deprecated = true, (.udpa.annotations.security) = { ... }
- Specified by:
hasHttp2ProtocolOptions
in interfaceClusterOrBuilder
- Returns:
- Whether the http2ProtocolOptions field is set.
-
getHttp2ProtocolOptions
@Deprecated public Http2ProtocolOptions getHttp2ProtocolOptions()
Deprecated.envoy.config.cluster.v3.Cluster.http2_protocol_options is deprecated. See envoy/config/cluster/v3/cluster.proto;l=933Even if default HTTP2 protocol options are desired, this field must be set so that Envoy will assume that the upstream supports HTTP/2 when making new HTTP connection pool connections. Currently, Envoy only supports prior knowledge for upstream connections. Even if TLS is used with ALPN, ``http2_protocol_options`` must be specified. As an aside this allows HTTP/2 connections to happen over plain text. This has been deprecated in favor of http2_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http2_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 14 [deprecated = true, (.udpa.annotations.security) = { ... }
- Specified by:
getHttp2ProtocolOptions
in interfaceClusterOrBuilder
- Returns:
- The http2ProtocolOptions.
-
setHttp2ProtocolOptions
@Deprecated public Cluster.Builder setHttp2ProtocolOptions(Http2ProtocolOptions value)
Deprecated.Even if default HTTP2 protocol options are desired, this field must be set so that Envoy will assume that the upstream supports HTTP/2 when making new HTTP connection pool connections. Currently, Envoy only supports prior knowledge for upstream connections. Even if TLS is used with ALPN, ``http2_protocol_options`` must be specified. As an aside this allows HTTP/2 connections to happen over plain text. This has been deprecated in favor of http2_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http2_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 14 [deprecated = true, (.udpa.annotations.security) = { ... }
-
setHttp2ProtocolOptions
@Deprecated public Cluster.Builder setHttp2ProtocolOptions(Http2ProtocolOptions.Builder builderForValue)
Deprecated.Even if default HTTP2 protocol options are desired, this field must be set so that Envoy will assume that the upstream supports HTTP/2 when making new HTTP connection pool connections. Currently, Envoy only supports prior knowledge for upstream connections. Even if TLS is used with ALPN, ``http2_protocol_options`` must be specified. As an aside this allows HTTP/2 connections to happen over plain text. This has been deprecated in favor of http2_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http2_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 14 [deprecated = true, (.udpa.annotations.security) = { ... }
-
mergeHttp2ProtocolOptions
@Deprecated public Cluster.Builder mergeHttp2ProtocolOptions(Http2ProtocolOptions value)
Deprecated.Even if default HTTP2 protocol options are desired, this field must be set so that Envoy will assume that the upstream supports HTTP/2 when making new HTTP connection pool connections. Currently, Envoy only supports prior knowledge for upstream connections. Even if TLS is used with ALPN, ``http2_protocol_options`` must be specified. As an aside this allows HTTP/2 connections to happen over plain text. This has been deprecated in favor of http2_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http2_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 14 [deprecated = true, (.udpa.annotations.security) = { ... }
-
clearHttp2ProtocolOptions
@Deprecated public Cluster.Builder clearHttp2ProtocolOptions()
Deprecated.Even if default HTTP2 protocol options are desired, this field must be set so that Envoy will assume that the upstream supports HTTP/2 when making new HTTP connection pool connections. Currently, Envoy only supports prior knowledge for upstream connections. Even if TLS is used with ALPN, ``http2_protocol_options`` must be specified. As an aside this allows HTTP/2 connections to happen over plain text. This has been deprecated in favor of http2_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http2_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 14 [deprecated = true, (.udpa.annotations.security) = { ... }
-
getHttp2ProtocolOptionsBuilder
@Deprecated public Http2ProtocolOptions.Builder getHttp2ProtocolOptionsBuilder()
Deprecated.Even if default HTTP2 protocol options are desired, this field must be set so that Envoy will assume that the upstream supports HTTP/2 when making new HTTP connection pool connections. Currently, Envoy only supports prior knowledge for upstream connections. Even if TLS is used with ALPN, ``http2_protocol_options`` must be specified. As an aside this allows HTTP/2 connections to happen over plain text. This has been deprecated in favor of http2_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http2_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 14 [deprecated = true, (.udpa.annotations.security) = { ... }
-
getHttp2ProtocolOptionsOrBuilder
@Deprecated public Http2ProtocolOptionsOrBuilder getHttp2ProtocolOptionsOrBuilder()
Deprecated.Even if default HTTP2 protocol options are desired, this field must be set so that Envoy will assume that the upstream supports HTTP/2 when making new HTTP connection pool connections. Currently, Envoy only supports prior knowledge for upstream connections. Even if TLS is used with ALPN, ``http2_protocol_options`` must be specified. As an aside this allows HTTP/2 connections to happen over plain text. This has been deprecated in favor of http2_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http2_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 14 [deprecated = true, (.udpa.annotations.security) = { ... }
- Specified by:
getHttp2ProtocolOptionsOrBuilder
in interfaceClusterOrBuilder
-
getHttp2ProtocolOptionsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Http2ProtocolOptions,Http2ProtocolOptions.Builder,Http2ProtocolOptionsOrBuilder> getHttp2ProtocolOptionsFieldBuilder()
Even if default HTTP2 protocol options are desired, this field must be set so that Envoy will assume that the upstream supports HTTP/2 when making new HTTP connection pool connections. Currently, Envoy only supports prior knowledge for upstream connections. Even if TLS is used with ALPN, ``http2_protocol_options`` must be specified. As an aside this allows HTTP/2 connections to happen over plain text. This has been deprecated in favor of http2_protocol_options fields in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http2_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`. See :ref:`upstream_http_protocol_options <envoy_v3_api_field_extensions.upstreams.http.v3.HttpProtocolOptions.upstream_http_protocol_options>` for example usage.
.envoy.config.core.v3.Http2ProtocolOptions http2_protocol_options = 14 [deprecated = true, (.udpa.annotations.security) = { ... }
-
internalGetTypedExtensionProtocolOptions
private com.google.protobuf.MapFieldBuilder<java.lang.String,com.google.protobuf.AnyOrBuilder,com.google.protobuf.Any,com.google.protobuf.Any.Builder> internalGetTypedExtensionProtocolOptions()
-
internalGetMutableTypedExtensionProtocolOptions
private com.google.protobuf.MapFieldBuilder<java.lang.String,com.google.protobuf.AnyOrBuilder,com.google.protobuf.Any,com.google.protobuf.Any.Builder> internalGetMutableTypedExtensionProtocolOptions()
-
getTypedExtensionProtocolOptionsCount
public int getTypedExtensionProtocolOptionsCount()
Description copied from interface:ClusterOrBuilder
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;
- Specified by:
getTypedExtensionProtocolOptionsCount
in interfaceClusterOrBuilder
-
containsTypedExtensionProtocolOptions
public boolean containsTypedExtensionProtocolOptions(java.lang.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;
- Specified by:
containsTypedExtensionProtocolOptions
in interfaceClusterOrBuilder
-
getTypedExtensionProtocolOptions
@Deprecated public java.util.Map<java.lang.String,com.google.protobuf.Any> getTypedExtensionProtocolOptions()
Deprecated.UsegetTypedExtensionProtocolOptionsMap()
instead.- Specified by:
getTypedExtensionProtocolOptions
in interfaceClusterOrBuilder
-
getTypedExtensionProtocolOptionsMap
public java.util.Map<java.lang.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;
- Specified by:
getTypedExtensionProtocolOptionsMap
in interfaceClusterOrBuilder
-
getTypedExtensionProtocolOptionsOrDefault
public com.google.protobuf.Any getTypedExtensionProtocolOptionsOrDefault(java.lang.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;
- Specified by:
getTypedExtensionProtocolOptionsOrDefault
in interfaceClusterOrBuilder
-
getTypedExtensionProtocolOptionsOrThrow
public com.google.protobuf.Any getTypedExtensionProtocolOptionsOrThrow(java.lang.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;
- Specified by:
getTypedExtensionProtocolOptionsOrThrow
in interfaceClusterOrBuilder
-
clearTypedExtensionProtocolOptions
public Cluster.Builder clearTypedExtensionProtocolOptions()
-
removeTypedExtensionProtocolOptions
public Cluster.Builder removeTypedExtensionProtocolOptions(java.lang.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;
-
getMutableTypedExtensionProtocolOptions
@Deprecated public java.util.Map<java.lang.String,com.google.protobuf.Any> getMutableTypedExtensionProtocolOptions()
Deprecated.Use alternate mutation accessors instead.
-
putTypedExtensionProtocolOptions
public Cluster.Builder putTypedExtensionProtocolOptions(java.lang.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;
-
putAllTypedExtensionProtocolOptions
public Cluster.Builder putAllTypedExtensionProtocolOptions(java.util.Map<java.lang.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;
-
putTypedExtensionProtocolOptionsBuilderIfAbsent
public com.google.protobuf.Any.Builder putTypedExtensionProtocolOptionsBuilderIfAbsent(java.lang.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;
-
hasDnsRefreshRate
public boolean hasDnsRefreshRate()
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }
- Specified by:
hasDnsRefreshRate
in interfaceClusterOrBuilder
- Returns:
- Whether the dnsRefreshRate field is set.
-
getDnsRefreshRate
public com.google.protobuf.Duration getDnsRefreshRate()
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }
- Specified by:
getDnsRefreshRate
in interfaceClusterOrBuilder
- Returns:
- The dnsRefreshRate.
-
setDnsRefreshRate
public 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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }
-
setDnsRefreshRate
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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }
-
mergeDnsRefreshRate
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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }
-
clearDnsRefreshRate
public Cluster.Builder clearDnsRefreshRate()
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }
-
getDnsRefreshRateBuilder
public com.google.protobuf.Duration.Builder getDnsRefreshRateBuilder()
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }
-
getDnsRefreshRateOrBuilder
public com.google.protobuf.DurationOrBuilder getDnsRefreshRateOrBuilder()
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }
- Specified by:
getDnsRefreshRateOrBuilder
in interfaceClusterOrBuilder
-
getDnsRefreshRateFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder,com.google.protobuf.DurationOrBuilder> getDnsRefreshRateFieldBuilder()
If the DNS refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.google.protobuf.Duration dns_refresh_rate = 16 [(.validate.rules) = { ... }
-
hasDnsFailureRefreshRate
public boolean hasDnsFailureRefreshRate()
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v3.Cluster.RefreshRate dns_failure_refresh_rate = 44;
- Specified by:
hasDnsFailureRefreshRate
in interfaceClusterOrBuilder
- Returns:
- Whether the dnsFailureRefreshRate field is set.
-
getDnsFailureRefreshRate
public Cluster.RefreshRate getDnsFailureRefreshRate()
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v3.Cluster.RefreshRate dns_failure_refresh_rate = 44;
- Specified by:
getDnsFailureRefreshRate
in interfaceClusterOrBuilder
- Returns:
- The dnsFailureRefreshRate.
-
setDnsFailureRefreshRate
public Cluster.Builder setDnsFailureRefreshRate(Cluster.RefreshRate value)
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v3.Cluster.RefreshRate dns_failure_refresh_rate = 44;
-
setDnsFailureRefreshRate
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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v3.Cluster.RefreshRate dns_failure_refresh_rate = 44;
-
mergeDnsFailureRefreshRate
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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v3.Cluster.RefreshRate dns_failure_refresh_rate = 44;
-
clearDnsFailureRefreshRate
public Cluster.Builder clearDnsFailureRefreshRate()
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v3.Cluster.RefreshRate dns_failure_refresh_rate = 44;
-
getDnsFailureRefreshRateBuilder
public Cluster.RefreshRate.Builder getDnsFailureRefreshRateBuilder()
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v3.Cluster.RefreshRate dns_failure_refresh_rate = 44;
-
getDnsFailureRefreshRateOrBuilder
public Cluster.RefreshRateOrBuilder getDnsFailureRefreshRateOrBuilder()
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v3.Cluster.RefreshRate dns_failure_refresh_rate = 44;
- Specified by:
getDnsFailureRefreshRateOrBuilder
in interfaceClusterOrBuilder
-
getDnsFailureRefreshRateFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Cluster.RefreshRate,Cluster.RefreshRate.Builder,Cluster.RefreshRateOrBuilder> getDnsFailureRefreshRateFieldBuilder()
If the DNS failure refresh rate is specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored.
.envoy.config.cluster.v3.Cluster.RefreshRate dns_failure_refresh_rate = 44;
-
getRespectDnsTtl
public 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;
- Specified by:
getRespectDnsTtl
in interfaceClusterOrBuilder
- Returns:
- The respectDnsTtl.
-
setRespectDnsTtl
public 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;
- Parameters:
value
- The respectDnsTtl to set.- Returns:
- This builder for chaining.
-
clearRespectDnsTtl
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;
- Returns:
- This builder for chaining.
-
getDnsLookupFamilyValue
public int getDnsLookupFamilyValue()
The DNS IP address resolution policy. If this setting is not specified, the value defaults to :ref:`AUTO<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DnsLookupFamily.AUTO>`.
.envoy.config.cluster.v3.Cluster.DnsLookupFamily dns_lookup_family = 17 [(.validate.rules) = { ... }
- Specified by:
getDnsLookupFamilyValue
in interfaceClusterOrBuilder
- Returns:
- The enum numeric value on the wire for dnsLookupFamily.
-
setDnsLookupFamilyValue
public Cluster.Builder setDnsLookupFamilyValue(int value)
The DNS IP address resolution policy. If this setting is not specified, the value defaults to :ref:`AUTO<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DnsLookupFamily.AUTO>`.
.envoy.config.cluster.v3.Cluster.DnsLookupFamily dns_lookup_family = 17 [(.validate.rules) = { ... }
- Parameters:
value
- The enum numeric value on the wire for dnsLookupFamily to set.- Returns:
- This builder for chaining.
-
getDnsLookupFamily
public Cluster.DnsLookupFamily getDnsLookupFamily()
The DNS IP address resolution policy. If this setting is not specified, the value defaults to :ref:`AUTO<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DnsLookupFamily.AUTO>`.
.envoy.config.cluster.v3.Cluster.DnsLookupFamily dns_lookup_family = 17 [(.validate.rules) = { ... }
- Specified by:
getDnsLookupFamily
in interfaceClusterOrBuilder
- Returns:
- The dnsLookupFamily.
-
setDnsLookupFamily
public 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_v3_api_enum_value_config.cluster.v3.Cluster.DnsLookupFamily.AUTO>`.
.envoy.config.cluster.v3.Cluster.DnsLookupFamily dns_lookup_family = 17 [(.validate.rules) = { ... }
- Parameters:
value
- The dnsLookupFamily to set.- Returns:
- This builder for chaining.
-
clearDnsLookupFamily
public Cluster.Builder clearDnsLookupFamily()
The DNS IP address resolution policy. If this setting is not specified, the value defaults to :ref:`AUTO<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DnsLookupFamily.AUTO>`.
.envoy.config.cluster.v3.Cluster.DnsLookupFamily dns_lookup_family = 17 [(.validate.rules) = { ... }
- Returns:
- This builder for chaining.
-
ensureDnsResolversIsMutable
private void ensureDnsResolversIsMutable()
-
getDnsResolversList
@Deprecated public java.util.List<Address> getDnsResolversList()
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getDnsResolversList
in interfaceClusterOrBuilder
-
getDnsResolversCount
@Deprecated public int getDnsResolversCount()
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getDnsResolversCount
in interfaceClusterOrBuilder
-
getDnsResolvers
@Deprecated public Address getDnsResolvers(int index)
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getDnsResolvers
in interfaceClusterOrBuilder
-
setDnsResolvers
@Deprecated public Cluster.Builder setDnsResolvers(int index, Address value)
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
setDnsResolvers
@Deprecated public Cluster.Builder setDnsResolvers(int index, Address.Builder builderForValue)
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
addDnsResolvers
@Deprecated public Cluster.Builder addDnsResolvers(Address value)
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
addDnsResolvers
@Deprecated public Cluster.Builder addDnsResolvers(int index, Address value)
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
addDnsResolvers
@Deprecated public Cluster.Builder addDnsResolvers(Address.Builder builderForValue)
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
addDnsResolvers
@Deprecated public Cluster.Builder addDnsResolvers(int index, Address.Builder builderForValue)
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
addAllDnsResolvers
@Deprecated public Cluster.Builder addAllDnsResolvers(java.lang.Iterable<? extends Address> values)
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
clearDnsResolvers
@Deprecated public Cluster.Builder clearDnsResolvers()
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
removeDnsResolvers
@Deprecated public Cluster.Builder removeDnsResolvers(int index)
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getDnsResolversBuilder
@Deprecated public Address.Builder getDnsResolversBuilder(int index)
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getDnsResolversOrBuilder
@Deprecated public AddressOrBuilder getDnsResolversOrBuilder(int index)
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getDnsResolversOrBuilder
in interfaceClusterOrBuilder
-
getDnsResolversOrBuilderList
@Deprecated public java.util.List<? extends AddressOrBuilder> getDnsResolversOrBuilderList()
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getDnsResolversOrBuilderList
in interfaceClusterOrBuilder
-
addDnsResolversBuilder
@Deprecated public Address.Builder addDnsResolversBuilder()
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
addDnsResolversBuilder
@Deprecated public Address.Builder addDnsResolversBuilder(int index)
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getDnsResolversBuilderList
@Deprecated public java.util.List<Address.Builder> getDnsResolversBuilderList()
Deprecated.If DNS resolvers are specified and the cluster type is either :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>` and :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>` this setting is ignored. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
repeated .envoy.config.core.v3.Address dns_resolvers = 18 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getDnsResolversFieldBuilder
private com.google.protobuf.RepeatedFieldBuilder<Address,Address.Builder,AddressOrBuilder> getDnsResolversFieldBuilder()
-
getUseTcpForDnsLookups
@Deprecated public boolean getUseTcpForDnsLookups()
Deprecated.envoy.config.cluster.v3.Cluster.use_tcp_for_dns_lookups is deprecated. See envoy/config/cluster/v3/cluster.proto;l=996Always use TCP queries instead of UDP queries for DNS lookups. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
bool use_tcp_for_dns_lookups = 45 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getUseTcpForDnsLookups
in interfaceClusterOrBuilder
- Returns:
- The useTcpForDnsLookups.
-
setUseTcpForDnsLookups
@Deprecated public Cluster.Builder setUseTcpForDnsLookups(boolean value)
Deprecated.envoy.config.cluster.v3.Cluster.use_tcp_for_dns_lookups is deprecated. See envoy/config/cluster/v3/cluster.proto;l=996Always use TCP queries instead of UDP queries for DNS lookups. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
bool use_tcp_for_dns_lookups = 45 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Parameters:
value
- The useTcpForDnsLookups to set.- Returns:
- This builder for chaining.
-
clearUseTcpForDnsLookups
@Deprecated public Cluster.Builder clearUseTcpForDnsLookups()
Deprecated.envoy.config.cluster.v3.Cluster.use_tcp_for_dns_lookups is deprecated. See envoy/config/cluster/v3/cluster.proto;l=996Always use TCP queries instead of UDP queries for DNS lookups. This field is deprecated in favor of ``dns_resolution_config`` which aggregates all of the DNS resolver configuration in a single message.
bool use_tcp_for_dns_lookups = 45 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Returns:
- This builder for chaining.
-
hasDnsResolutionConfig
@Deprecated public boolean hasDnsResolutionConfig()
Deprecated.envoy.config.cluster.v3.Cluster.dns_resolution_config is deprecated. See envoy/config/cluster/v3/cluster.proto;l=1002DNS resolution configuration which includes the underlying dns resolver addresses and options. This field is deprecated in favor of :ref:`typed_dns_resolver_config <envoy_v3_api_field_config.cluster.v3.Cluster.typed_dns_resolver_config>`.
.envoy.config.core.v3.DnsResolutionConfig dns_resolution_config = 53 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
hasDnsResolutionConfig
in interfaceClusterOrBuilder
- Returns:
- Whether the dnsResolutionConfig field is set.
-
getDnsResolutionConfig
@Deprecated public DnsResolutionConfig getDnsResolutionConfig()
Deprecated.envoy.config.cluster.v3.Cluster.dns_resolution_config is deprecated. See envoy/config/cluster/v3/cluster.proto;l=1002DNS resolution configuration which includes the underlying dns resolver addresses and options. This field is deprecated in favor of :ref:`typed_dns_resolver_config <envoy_v3_api_field_config.cluster.v3.Cluster.typed_dns_resolver_config>`.
.envoy.config.core.v3.DnsResolutionConfig dns_resolution_config = 53 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getDnsResolutionConfig
in interfaceClusterOrBuilder
- Returns:
- The dnsResolutionConfig.
-
setDnsResolutionConfig
@Deprecated public Cluster.Builder setDnsResolutionConfig(DnsResolutionConfig value)
Deprecated.DNS resolution configuration which includes the underlying dns resolver addresses and options. This field is deprecated in favor of :ref:`typed_dns_resolver_config <envoy_v3_api_field_config.cluster.v3.Cluster.typed_dns_resolver_config>`.
.envoy.config.core.v3.DnsResolutionConfig dns_resolution_config = 53 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
setDnsResolutionConfig
@Deprecated public Cluster.Builder setDnsResolutionConfig(DnsResolutionConfig.Builder builderForValue)
Deprecated.DNS resolution configuration which includes the underlying dns resolver addresses and options. This field is deprecated in favor of :ref:`typed_dns_resolver_config <envoy_v3_api_field_config.cluster.v3.Cluster.typed_dns_resolver_config>`.
.envoy.config.core.v3.DnsResolutionConfig dns_resolution_config = 53 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
mergeDnsResolutionConfig
@Deprecated public Cluster.Builder mergeDnsResolutionConfig(DnsResolutionConfig value)
Deprecated.DNS resolution configuration which includes the underlying dns resolver addresses and options. This field is deprecated in favor of :ref:`typed_dns_resolver_config <envoy_v3_api_field_config.cluster.v3.Cluster.typed_dns_resolver_config>`.
.envoy.config.core.v3.DnsResolutionConfig dns_resolution_config = 53 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
clearDnsResolutionConfig
@Deprecated public Cluster.Builder clearDnsResolutionConfig()
Deprecated.DNS resolution configuration which includes the underlying dns resolver addresses and options. This field is deprecated in favor of :ref:`typed_dns_resolver_config <envoy_v3_api_field_config.cluster.v3.Cluster.typed_dns_resolver_config>`.
.envoy.config.core.v3.DnsResolutionConfig dns_resolution_config = 53 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getDnsResolutionConfigBuilder
@Deprecated public DnsResolutionConfig.Builder getDnsResolutionConfigBuilder()
Deprecated.DNS resolution configuration which includes the underlying dns resolver addresses and options. This field is deprecated in favor of :ref:`typed_dns_resolver_config <envoy_v3_api_field_config.cluster.v3.Cluster.typed_dns_resolver_config>`.
.envoy.config.core.v3.DnsResolutionConfig dns_resolution_config = 53 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
getDnsResolutionConfigOrBuilder
@Deprecated public DnsResolutionConfigOrBuilder getDnsResolutionConfigOrBuilder()
Deprecated.DNS resolution configuration which includes the underlying dns resolver addresses and options. This field is deprecated in favor of :ref:`typed_dns_resolver_config <envoy_v3_api_field_config.cluster.v3.Cluster.typed_dns_resolver_config>`.
.envoy.config.core.v3.DnsResolutionConfig dns_resolution_config = 53 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getDnsResolutionConfigOrBuilder
in interfaceClusterOrBuilder
-
getDnsResolutionConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<DnsResolutionConfig,DnsResolutionConfig.Builder,DnsResolutionConfigOrBuilder> getDnsResolutionConfigFieldBuilder()
DNS resolution configuration which includes the underlying dns resolver addresses and options. This field is deprecated in favor of :ref:`typed_dns_resolver_config <envoy_v3_api_field_config.cluster.v3.Cluster.typed_dns_resolver_config>`.
.envoy.config.core.v3.DnsResolutionConfig dns_resolution_config = 53 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
-
hasTypedDnsResolverConfig
public boolean hasTypedDnsResolverConfig()
DNS resolver type configuration extension. This extension can be used to configure c-ares, apple, or any other DNS resolver types and the related parameters. For example, an object of :ref:`CaresDnsResolverConfig <envoy_v3_api_msg_extensions.network.dns_resolver.cares.v3.CaresDnsResolverConfig>` can be packed into this ``typed_dns_resolver_config``. This configuration replaces the :ref:`dns_resolution_config <envoy_v3_api_field_config.cluster.v3.Cluster.dns_resolution_config>` configuration. During the transition period when both ``dns_resolution_config`` and ``typed_dns_resolver_config`` exists, when ``typed_dns_resolver_config`` is in place, Envoy will use it and ignore ``dns_resolution_config``. When ``typed_dns_resolver_config`` is missing, the default behavior is in place. [#extension-category: envoy.network.dns_resolver]
.envoy.config.core.v3.TypedExtensionConfig typed_dns_resolver_config = 55;
- Specified by:
hasTypedDnsResolverConfig
in interfaceClusterOrBuilder
- Returns:
- Whether the typedDnsResolverConfig field is set.
-
getTypedDnsResolverConfig
public TypedExtensionConfig getTypedDnsResolverConfig()
DNS resolver type configuration extension. This extension can be used to configure c-ares, apple, or any other DNS resolver types and the related parameters. For example, an object of :ref:`CaresDnsResolverConfig <envoy_v3_api_msg_extensions.network.dns_resolver.cares.v3.CaresDnsResolverConfig>` can be packed into this ``typed_dns_resolver_config``. This configuration replaces the :ref:`dns_resolution_config <envoy_v3_api_field_config.cluster.v3.Cluster.dns_resolution_config>` configuration. During the transition period when both ``dns_resolution_config`` and ``typed_dns_resolver_config`` exists, when ``typed_dns_resolver_config`` is in place, Envoy will use it and ignore ``dns_resolution_config``. When ``typed_dns_resolver_config`` is missing, the default behavior is in place. [#extension-category: envoy.network.dns_resolver]
.envoy.config.core.v3.TypedExtensionConfig typed_dns_resolver_config = 55;
- Specified by:
getTypedDnsResolverConfig
in interfaceClusterOrBuilder
- Returns:
- The typedDnsResolverConfig.
-
setTypedDnsResolverConfig
public Cluster.Builder setTypedDnsResolverConfig(TypedExtensionConfig value)
DNS resolver type configuration extension. This extension can be used to configure c-ares, apple, or any other DNS resolver types and the related parameters. For example, an object of :ref:`CaresDnsResolverConfig <envoy_v3_api_msg_extensions.network.dns_resolver.cares.v3.CaresDnsResolverConfig>` can be packed into this ``typed_dns_resolver_config``. This configuration replaces the :ref:`dns_resolution_config <envoy_v3_api_field_config.cluster.v3.Cluster.dns_resolution_config>` configuration. During the transition period when both ``dns_resolution_config`` and ``typed_dns_resolver_config`` exists, when ``typed_dns_resolver_config`` is in place, Envoy will use it and ignore ``dns_resolution_config``. When ``typed_dns_resolver_config`` is missing, the default behavior is in place. [#extension-category: envoy.network.dns_resolver]
.envoy.config.core.v3.TypedExtensionConfig typed_dns_resolver_config = 55;
-
setTypedDnsResolverConfig
public Cluster.Builder setTypedDnsResolverConfig(TypedExtensionConfig.Builder builderForValue)
DNS resolver type configuration extension. This extension can be used to configure c-ares, apple, or any other DNS resolver types and the related parameters. For example, an object of :ref:`CaresDnsResolverConfig <envoy_v3_api_msg_extensions.network.dns_resolver.cares.v3.CaresDnsResolverConfig>` can be packed into this ``typed_dns_resolver_config``. This configuration replaces the :ref:`dns_resolution_config <envoy_v3_api_field_config.cluster.v3.Cluster.dns_resolution_config>` configuration. During the transition period when both ``dns_resolution_config`` and ``typed_dns_resolver_config`` exists, when ``typed_dns_resolver_config`` is in place, Envoy will use it and ignore ``dns_resolution_config``. When ``typed_dns_resolver_config`` is missing, the default behavior is in place. [#extension-category: envoy.network.dns_resolver]
.envoy.config.core.v3.TypedExtensionConfig typed_dns_resolver_config = 55;
-
mergeTypedDnsResolverConfig
public Cluster.Builder mergeTypedDnsResolverConfig(TypedExtensionConfig value)
DNS resolver type configuration extension. This extension can be used to configure c-ares, apple, or any other DNS resolver types and the related parameters. For example, an object of :ref:`CaresDnsResolverConfig <envoy_v3_api_msg_extensions.network.dns_resolver.cares.v3.CaresDnsResolverConfig>` can be packed into this ``typed_dns_resolver_config``. This configuration replaces the :ref:`dns_resolution_config <envoy_v3_api_field_config.cluster.v3.Cluster.dns_resolution_config>` configuration. During the transition period when both ``dns_resolution_config`` and ``typed_dns_resolver_config`` exists, when ``typed_dns_resolver_config`` is in place, Envoy will use it and ignore ``dns_resolution_config``. When ``typed_dns_resolver_config`` is missing, the default behavior is in place. [#extension-category: envoy.network.dns_resolver]
.envoy.config.core.v3.TypedExtensionConfig typed_dns_resolver_config = 55;
-
clearTypedDnsResolverConfig
public Cluster.Builder clearTypedDnsResolverConfig()
DNS resolver type configuration extension. This extension can be used to configure c-ares, apple, or any other DNS resolver types and the related parameters. For example, an object of :ref:`CaresDnsResolverConfig <envoy_v3_api_msg_extensions.network.dns_resolver.cares.v3.CaresDnsResolverConfig>` can be packed into this ``typed_dns_resolver_config``. This configuration replaces the :ref:`dns_resolution_config <envoy_v3_api_field_config.cluster.v3.Cluster.dns_resolution_config>` configuration. During the transition period when both ``dns_resolution_config`` and ``typed_dns_resolver_config`` exists, when ``typed_dns_resolver_config`` is in place, Envoy will use it and ignore ``dns_resolution_config``. When ``typed_dns_resolver_config`` is missing, the default behavior is in place. [#extension-category: envoy.network.dns_resolver]
.envoy.config.core.v3.TypedExtensionConfig typed_dns_resolver_config = 55;
-
getTypedDnsResolverConfigBuilder
public TypedExtensionConfig.Builder getTypedDnsResolverConfigBuilder()
DNS resolver type configuration extension. This extension can be used to configure c-ares, apple, or any other DNS resolver types and the related parameters. For example, an object of :ref:`CaresDnsResolverConfig <envoy_v3_api_msg_extensions.network.dns_resolver.cares.v3.CaresDnsResolverConfig>` can be packed into this ``typed_dns_resolver_config``. This configuration replaces the :ref:`dns_resolution_config <envoy_v3_api_field_config.cluster.v3.Cluster.dns_resolution_config>` configuration. During the transition period when both ``dns_resolution_config`` and ``typed_dns_resolver_config`` exists, when ``typed_dns_resolver_config`` is in place, Envoy will use it and ignore ``dns_resolution_config``. When ``typed_dns_resolver_config`` is missing, the default behavior is in place. [#extension-category: envoy.network.dns_resolver]
.envoy.config.core.v3.TypedExtensionConfig typed_dns_resolver_config = 55;
-
getTypedDnsResolverConfigOrBuilder
public TypedExtensionConfigOrBuilder getTypedDnsResolverConfigOrBuilder()
DNS resolver type configuration extension. This extension can be used to configure c-ares, apple, or any other DNS resolver types and the related parameters. For example, an object of :ref:`CaresDnsResolverConfig <envoy_v3_api_msg_extensions.network.dns_resolver.cares.v3.CaresDnsResolverConfig>` can be packed into this ``typed_dns_resolver_config``. This configuration replaces the :ref:`dns_resolution_config <envoy_v3_api_field_config.cluster.v3.Cluster.dns_resolution_config>` configuration. During the transition period when both ``dns_resolution_config`` and ``typed_dns_resolver_config`` exists, when ``typed_dns_resolver_config`` is in place, Envoy will use it and ignore ``dns_resolution_config``. When ``typed_dns_resolver_config`` is missing, the default behavior is in place. [#extension-category: envoy.network.dns_resolver]
.envoy.config.core.v3.TypedExtensionConfig typed_dns_resolver_config = 55;
- Specified by:
getTypedDnsResolverConfigOrBuilder
in interfaceClusterOrBuilder
-
getTypedDnsResolverConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder,TypedExtensionConfigOrBuilder> getTypedDnsResolverConfigFieldBuilder()
DNS resolver type configuration extension. This extension can be used to configure c-ares, apple, or any other DNS resolver types and the related parameters. For example, an object of :ref:`CaresDnsResolverConfig <envoy_v3_api_msg_extensions.network.dns_resolver.cares.v3.CaresDnsResolverConfig>` can be packed into this ``typed_dns_resolver_config``. This configuration replaces the :ref:`dns_resolution_config <envoy_v3_api_field_config.cluster.v3.Cluster.dns_resolution_config>` configuration. During the transition period when both ``dns_resolution_config`` and ``typed_dns_resolver_config`` exists, when ``typed_dns_resolver_config`` is in place, Envoy will use it and ignore ``dns_resolution_config``. When ``typed_dns_resolver_config`` is missing, the default behavior is in place. [#extension-category: envoy.network.dns_resolver]
.envoy.config.core.v3.TypedExtensionConfig typed_dns_resolver_config = 55;
-
hasWaitForWarmOnInit
public boolean hasWaitForWarmOnInit()
Optional configuration for having cluster readiness block on warm-up. Currently, only applicable for :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, or :ref:`Redis Cluster<arch_overview_redis>`. If true, cluster readiness blocks on warm-up. If false, the cluster will complete initialization whether or not warm-up has completed. Defaults to true.
.google.protobuf.BoolValue wait_for_warm_on_init = 54;
- Specified by:
hasWaitForWarmOnInit
in interfaceClusterOrBuilder
- Returns:
- Whether the waitForWarmOnInit field is set.
-
getWaitForWarmOnInit
public com.google.protobuf.BoolValue getWaitForWarmOnInit()
Optional configuration for having cluster readiness block on warm-up. Currently, only applicable for :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, or :ref:`Redis Cluster<arch_overview_redis>`. If true, cluster readiness blocks on warm-up. If false, the cluster will complete initialization whether or not warm-up has completed. Defaults to true.
.google.protobuf.BoolValue wait_for_warm_on_init = 54;
- Specified by:
getWaitForWarmOnInit
in interfaceClusterOrBuilder
- Returns:
- The waitForWarmOnInit.
-
setWaitForWarmOnInit
public Cluster.Builder setWaitForWarmOnInit(com.google.protobuf.BoolValue value)
Optional configuration for having cluster readiness block on warm-up. Currently, only applicable for :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, or :ref:`Redis Cluster<arch_overview_redis>`. If true, cluster readiness blocks on warm-up. If false, the cluster will complete initialization whether or not warm-up has completed. Defaults to true.
.google.protobuf.BoolValue wait_for_warm_on_init = 54;
-
setWaitForWarmOnInit
public Cluster.Builder setWaitForWarmOnInit(com.google.protobuf.BoolValue.Builder builderForValue)
Optional configuration for having cluster readiness block on warm-up. Currently, only applicable for :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, or :ref:`Redis Cluster<arch_overview_redis>`. If true, cluster readiness blocks on warm-up. If false, the cluster will complete initialization whether or not warm-up has completed. Defaults to true.
.google.protobuf.BoolValue wait_for_warm_on_init = 54;
-
mergeWaitForWarmOnInit
public Cluster.Builder mergeWaitForWarmOnInit(com.google.protobuf.BoolValue value)
Optional configuration for having cluster readiness block on warm-up. Currently, only applicable for :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, or :ref:`Redis Cluster<arch_overview_redis>`. If true, cluster readiness blocks on warm-up. If false, the cluster will complete initialization whether or not warm-up has completed. Defaults to true.
.google.protobuf.BoolValue wait_for_warm_on_init = 54;
-
clearWaitForWarmOnInit
public Cluster.Builder clearWaitForWarmOnInit()
Optional configuration for having cluster readiness block on warm-up. Currently, only applicable for :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, or :ref:`Redis Cluster<arch_overview_redis>`. If true, cluster readiness blocks on warm-up. If false, the cluster will complete initialization whether or not warm-up has completed. Defaults to true.
.google.protobuf.BoolValue wait_for_warm_on_init = 54;
-
getWaitForWarmOnInitBuilder
public com.google.protobuf.BoolValue.Builder getWaitForWarmOnInitBuilder()
Optional configuration for having cluster readiness block on warm-up. Currently, only applicable for :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, or :ref:`Redis Cluster<arch_overview_redis>`. If true, cluster readiness blocks on warm-up. If false, the cluster will complete initialization whether or not warm-up has completed. Defaults to true.
.google.protobuf.BoolValue wait_for_warm_on_init = 54;
-
getWaitForWarmOnInitOrBuilder
public com.google.protobuf.BoolValueOrBuilder getWaitForWarmOnInitOrBuilder()
Optional configuration for having cluster readiness block on warm-up. Currently, only applicable for :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, or :ref:`Redis Cluster<arch_overview_redis>`. If true, cluster readiness blocks on warm-up. If false, the cluster will complete initialization whether or not warm-up has completed. Defaults to true.
.google.protobuf.BoolValue wait_for_warm_on_init = 54;
- Specified by:
getWaitForWarmOnInitOrBuilder
in interfaceClusterOrBuilder
-
getWaitForWarmOnInitFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.BoolValue,com.google.protobuf.BoolValue.Builder,com.google.protobuf.BoolValueOrBuilder> getWaitForWarmOnInitFieldBuilder()
Optional configuration for having cluster readiness block on warm-up. Currently, only applicable for :ref:`STRICT_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.STRICT_DNS>`, or :ref:`LOGICAL_DNS<envoy_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.LOGICAL_DNS>`, or :ref:`Redis Cluster<arch_overview_redis>`. If true, cluster readiness blocks on warm-up. If false, the cluster will complete initialization whether or not warm-up has completed. Defaults to true.
.google.protobuf.BoolValue wait_for_warm_on_init = 54;
-
hasOutlierDetection
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.v3.OutlierDetection outlier_detection = 19;
- Specified by:
hasOutlierDetection
in interfaceClusterOrBuilder
- Returns:
- Whether the outlierDetection field is set.
-
getOutlierDetection
public 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.v3.OutlierDetection outlier_detection = 19;
- Specified by:
getOutlierDetection
in interfaceClusterOrBuilder
- Returns:
- The outlierDetection.
-
setOutlierDetection
public 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.v3.OutlierDetection outlier_detection = 19;
-
setOutlierDetection
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.v3.OutlierDetection outlier_detection = 19;
-
mergeOutlierDetection
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.v3.OutlierDetection outlier_detection = 19;
-
clearOutlierDetection
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.v3.OutlierDetection outlier_detection = 19;
-
getOutlierDetectionBuilder
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.v3.OutlierDetection outlier_detection = 19;
-
getOutlierDetectionOrBuilder
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.v3.OutlierDetection outlier_detection = 19;
- Specified by:
getOutlierDetectionOrBuilder
in interfaceClusterOrBuilder
-
getOutlierDetectionFieldBuilder
private com.google.protobuf.SingleFieldBuilder<OutlierDetection,OutlierDetection.Builder,OutlierDetectionOrBuilder> getOutlierDetectionFieldBuilder()
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.v3.OutlierDetection outlier_detection = 19;
-
hasCleanupInterval
public boolean hasCleanupInterval()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }
- Specified by:
hasCleanupInterval
in interfaceClusterOrBuilder
- Returns:
- Whether the cleanupInterval field is set.
-
getCleanupInterval
public com.google.protobuf.Duration getCleanupInterval()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }
- Specified by:
getCleanupInterval
in interfaceClusterOrBuilder
- Returns:
- The cleanupInterval.
-
setCleanupInterval
public Cluster.Builder setCleanupInterval(com.google.protobuf.Duration value)
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }
-
setCleanupInterval
public Cluster.Builder setCleanupInterval(com.google.protobuf.Duration.Builder builderForValue)
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }
-
mergeCleanupInterval
public Cluster.Builder mergeCleanupInterval(com.google.protobuf.Duration value)
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }
-
clearCleanupInterval
public Cluster.Builder clearCleanupInterval()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }
-
getCleanupIntervalBuilder
public com.google.protobuf.Duration.Builder getCleanupIntervalBuilder()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }
-
getCleanupIntervalOrBuilder
public com.google.protobuf.DurationOrBuilder getCleanupIntervalOrBuilder()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }
- Specified by:
getCleanupIntervalOrBuilder
in interfaceClusterOrBuilder
-
getCleanupIntervalFieldBuilder
private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,com.google.protobuf.Duration.Builder,com.google.protobuf.DurationOrBuilder> getCleanupIntervalFieldBuilder()
The interval for removing stale hosts from a cluster type :ref:`ORIGINAL_DST<envoy_v3_api_enum_value_config.cluster.v3.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_v3_api_enum_value_config.cluster.v3.Cluster.DiscoveryType.ORIGINAL_DST>` this setting is ignored.
.google.protobuf.Duration cleanup_interval = 20 [(.validate.rules) = { ... }
-
hasUpstreamBindConfig
public 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.v3.BindConfig upstream_bind_config = 21;
- Specified by:
hasUpstreamBindConfig
in interfaceClusterOrBuilder
- Returns:
- Whether the upstreamBindConfig field is set.
-
getUpstreamBindConfig
public 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.v3.BindConfig upstream_bind_config = 21;
- Specified by:
getUpstreamBindConfig
in interfaceClusterOrBuilder
- Returns:
- The upstreamBindConfig.
-
setUpstreamBindConfig
public 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.v3.BindConfig upstream_bind_config = 21;
-
setUpstreamBindConfig
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.v3.BindConfig upstream_bind_config = 21;
-
mergeUpstreamBindConfig
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.v3.BindConfig upstream_bind_config = 21;
-
clearUpstreamBindConfig
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.v3.BindConfig upstream_bind_config = 21;
-
getUpstreamBindConfigBuilder
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.v3.BindConfig upstream_bind_config = 21;
-
getUpstreamBindConfigOrBuilder
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.v3.BindConfig upstream_bind_config = 21;
- Specified by:
getUpstreamBindConfigOrBuilder
in interfaceClusterOrBuilder
-
getUpstreamBindConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<BindConfig,BindConfig.Builder,BindConfigOrBuilder> getUpstreamBindConfigFieldBuilder()
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.v3.BindConfig upstream_bind_config = 21;
-
hasLbSubsetConfig
public boolean hasLbSubsetConfig()
Configuration for load balancing subsetting.
.envoy.config.cluster.v3.Cluster.LbSubsetConfig lb_subset_config = 22;
- Specified by:
hasLbSubsetConfig
in interfaceClusterOrBuilder
- Returns:
- Whether the lbSubsetConfig field is set.
-
getLbSubsetConfig
public Cluster.LbSubsetConfig getLbSubsetConfig()
Configuration for load balancing subsetting.
.envoy.config.cluster.v3.Cluster.LbSubsetConfig lb_subset_config = 22;
- Specified by:
getLbSubsetConfig
in interfaceClusterOrBuilder
- Returns:
- The lbSubsetConfig.
-
setLbSubsetConfig
public Cluster.Builder setLbSubsetConfig(Cluster.LbSubsetConfig value)
Configuration for load balancing subsetting.
.envoy.config.cluster.v3.Cluster.LbSubsetConfig lb_subset_config = 22;
-
setLbSubsetConfig
public Cluster.Builder setLbSubsetConfig(Cluster.LbSubsetConfig.Builder builderForValue)
Configuration for load balancing subsetting.
.envoy.config.cluster.v3.Cluster.LbSubsetConfig lb_subset_config = 22;
-
mergeLbSubsetConfig
public Cluster.Builder mergeLbSubsetConfig(Cluster.LbSubsetConfig value)
Configuration for load balancing subsetting.
.envoy.config.cluster.v3.Cluster.LbSubsetConfig lb_subset_config = 22;
-
clearLbSubsetConfig
public Cluster.Builder clearLbSubsetConfig()
Configuration for load balancing subsetting.
.envoy.config.cluster.v3.Cluster.LbSubsetConfig lb_subset_config = 22;
-
getLbSubsetConfigBuilder
public Cluster.LbSubsetConfig.Builder getLbSubsetConfigBuilder()
Configuration for load balancing subsetting.
.envoy.config.cluster.v3.Cluster.LbSubsetConfig lb_subset_config = 22;
-
getLbSubsetConfigOrBuilder
public Cluster.LbSubsetConfigOrBuilder getLbSubsetConfigOrBuilder()
Configuration for load balancing subsetting.
.envoy.config.cluster.v3.Cluster.LbSubsetConfig lb_subset_config = 22;
- Specified by:
getLbSubsetConfigOrBuilder
in interfaceClusterOrBuilder
-
getLbSubsetConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Cluster.LbSubsetConfig,Cluster.LbSubsetConfig.Builder,Cluster.LbSubsetConfigOrBuilder> getLbSubsetConfigFieldBuilder()
Configuration for load balancing subsetting.
.envoy.config.cluster.v3.Cluster.LbSubsetConfig lb_subset_config = 22;
-
hasRingHashLbConfig
public boolean hasRingHashLbConfig()
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v3.Cluster.RingHashLbConfig ring_hash_lb_config = 23;
- Specified by:
hasRingHashLbConfig
in interfaceClusterOrBuilder
- Returns:
- Whether the ringHashLbConfig field is set.
-
getRingHashLbConfig
public Cluster.RingHashLbConfig getRingHashLbConfig()
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v3.Cluster.RingHashLbConfig ring_hash_lb_config = 23;
- Specified by:
getRingHashLbConfig
in interfaceClusterOrBuilder
- Returns:
- The ringHashLbConfig.
-
setRingHashLbConfig
public Cluster.Builder setRingHashLbConfig(Cluster.RingHashLbConfig value)
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v3.Cluster.RingHashLbConfig ring_hash_lb_config = 23;
-
setRingHashLbConfig
public Cluster.Builder setRingHashLbConfig(Cluster.RingHashLbConfig.Builder builderForValue)
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v3.Cluster.RingHashLbConfig ring_hash_lb_config = 23;
-
mergeRingHashLbConfig
public Cluster.Builder mergeRingHashLbConfig(Cluster.RingHashLbConfig value)
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v3.Cluster.RingHashLbConfig ring_hash_lb_config = 23;
-
clearRingHashLbConfig
public Cluster.Builder clearRingHashLbConfig()
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v3.Cluster.RingHashLbConfig ring_hash_lb_config = 23;
-
getRingHashLbConfigBuilder
public Cluster.RingHashLbConfig.Builder getRingHashLbConfigBuilder()
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v3.Cluster.RingHashLbConfig ring_hash_lb_config = 23;
-
getRingHashLbConfigOrBuilder
public Cluster.RingHashLbConfigOrBuilder getRingHashLbConfigOrBuilder()
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v3.Cluster.RingHashLbConfig ring_hash_lb_config = 23;
- Specified by:
getRingHashLbConfigOrBuilder
in interfaceClusterOrBuilder
-
getRingHashLbConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Cluster.RingHashLbConfig,Cluster.RingHashLbConfig.Builder,Cluster.RingHashLbConfigOrBuilder> getRingHashLbConfigFieldBuilder()
Optional configuration for the Ring Hash load balancing policy.
.envoy.config.cluster.v3.Cluster.RingHashLbConfig ring_hash_lb_config = 23;
-
hasMaglevLbConfig
public boolean hasMaglevLbConfig()
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v3.Cluster.MaglevLbConfig maglev_lb_config = 52;
- Specified by:
hasMaglevLbConfig
in interfaceClusterOrBuilder
- Returns:
- Whether the maglevLbConfig field is set.
-
getMaglevLbConfig
public Cluster.MaglevLbConfig getMaglevLbConfig()
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v3.Cluster.MaglevLbConfig maglev_lb_config = 52;
- Specified by:
getMaglevLbConfig
in interfaceClusterOrBuilder
- Returns:
- The maglevLbConfig.
-
setMaglevLbConfig
public Cluster.Builder setMaglevLbConfig(Cluster.MaglevLbConfig value)
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v3.Cluster.MaglevLbConfig maglev_lb_config = 52;
-
setMaglevLbConfig
public Cluster.Builder setMaglevLbConfig(Cluster.MaglevLbConfig.Builder builderForValue)
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v3.Cluster.MaglevLbConfig maglev_lb_config = 52;
-
mergeMaglevLbConfig
public Cluster.Builder mergeMaglevLbConfig(Cluster.MaglevLbConfig value)
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v3.Cluster.MaglevLbConfig maglev_lb_config = 52;
-
clearMaglevLbConfig
public Cluster.Builder clearMaglevLbConfig()
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v3.Cluster.MaglevLbConfig maglev_lb_config = 52;
-
getMaglevLbConfigBuilder
public Cluster.MaglevLbConfig.Builder getMaglevLbConfigBuilder()
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v3.Cluster.MaglevLbConfig maglev_lb_config = 52;
-
getMaglevLbConfigOrBuilder
public Cluster.MaglevLbConfigOrBuilder getMaglevLbConfigOrBuilder()
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v3.Cluster.MaglevLbConfig maglev_lb_config = 52;
- Specified by:
getMaglevLbConfigOrBuilder
in interfaceClusterOrBuilder
-
getMaglevLbConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Cluster.MaglevLbConfig,Cluster.MaglevLbConfig.Builder,Cluster.MaglevLbConfigOrBuilder> getMaglevLbConfigFieldBuilder()
Optional configuration for the Maglev load balancing policy.
.envoy.config.cluster.v3.Cluster.MaglevLbConfig maglev_lb_config = 52;
-
hasOriginalDstLbConfig
public boolean hasOriginalDstLbConfig()
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v3.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;
- Specified by:
hasOriginalDstLbConfig
in interfaceClusterOrBuilder
- Returns:
- Whether the originalDstLbConfig field is set.
-
getOriginalDstLbConfig
public Cluster.OriginalDstLbConfig getOriginalDstLbConfig()
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v3.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;
- Specified by:
getOriginalDstLbConfig
in interfaceClusterOrBuilder
- Returns:
- The originalDstLbConfig.
-
setOriginalDstLbConfig
public Cluster.Builder setOriginalDstLbConfig(Cluster.OriginalDstLbConfig value)
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v3.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;
-
setOriginalDstLbConfig
public Cluster.Builder setOriginalDstLbConfig(Cluster.OriginalDstLbConfig.Builder builderForValue)
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v3.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;
-
mergeOriginalDstLbConfig
public Cluster.Builder mergeOriginalDstLbConfig(Cluster.OriginalDstLbConfig value)
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v3.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;
-
clearOriginalDstLbConfig
public Cluster.Builder clearOriginalDstLbConfig()
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v3.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;
-
getOriginalDstLbConfigBuilder
public Cluster.OriginalDstLbConfig.Builder getOriginalDstLbConfigBuilder()
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v3.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;
-
getOriginalDstLbConfigOrBuilder
public Cluster.OriginalDstLbConfigOrBuilder getOriginalDstLbConfigOrBuilder()
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v3.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;
- Specified by:
getOriginalDstLbConfigOrBuilder
in interfaceClusterOrBuilder
-
getOriginalDstLbConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Cluster.OriginalDstLbConfig,Cluster.OriginalDstLbConfig.Builder,Cluster.OriginalDstLbConfigOrBuilder> getOriginalDstLbConfigFieldBuilder()
Optional configuration for the Original Destination load balancing policy.
.envoy.config.cluster.v3.Cluster.OriginalDstLbConfig original_dst_lb_config = 34;
-
hasLeastRequestLbConfig
public boolean hasLeastRequestLbConfig()
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v3.Cluster.LeastRequestLbConfig least_request_lb_config = 37;
- Specified by:
hasLeastRequestLbConfig
in interfaceClusterOrBuilder
- Returns:
- Whether the leastRequestLbConfig field is set.
-
getLeastRequestLbConfig
public Cluster.LeastRequestLbConfig getLeastRequestLbConfig()
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v3.Cluster.LeastRequestLbConfig least_request_lb_config = 37;
- Specified by:
getLeastRequestLbConfig
in interfaceClusterOrBuilder
- Returns:
- The leastRequestLbConfig.
-
setLeastRequestLbConfig
public Cluster.Builder setLeastRequestLbConfig(Cluster.LeastRequestLbConfig value)
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v3.Cluster.LeastRequestLbConfig least_request_lb_config = 37;
-
setLeastRequestLbConfig
public Cluster.Builder setLeastRequestLbConfig(Cluster.LeastRequestLbConfig.Builder builderForValue)
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v3.Cluster.LeastRequestLbConfig least_request_lb_config = 37;
-
mergeLeastRequestLbConfig
public Cluster.Builder mergeLeastRequestLbConfig(Cluster.LeastRequestLbConfig value)
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v3.Cluster.LeastRequestLbConfig least_request_lb_config = 37;
-
clearLeastRequestLbConfig
public Cluster.Builder clearLeastRequestLbConfig()
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v3.Cluster.LeastRequestLbConfig least_request_lb_config = 37;
-
getLeastRequestLbConfigBuilder
public Cluster.LeastRequestLbConfig.Builder getLeastRequestLbConfigBuilder()
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v3.Cluster.LeastRequestLbConfig least_request_lb_config = 37;
-
getLeastRequestLbConfigOrBuilder
public Cluster.LeastRequestLbConfigOrBuilder getLeastRequestLbConfigOrBuilder()
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v3.Cluster.LeastRequestLbConfig least_request_lb_config = 37;
- Specified by:
getLeastRequestLbConfigOrBuilder
in interfaceClusterOrBuilder
-
getLeastRequestLbConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Cluster.LeastRequestLbConfig,Cluster.LeastRequestLbConfig.Builder,Cluster.LeastRequestLbConfigOrBuilder> getLeastRequestLbConfigFieldBuilder()
Optional configuration for the LeastRequest load balancing policy.
.envoy.config.cluster.v3.Cluster.LeastRequestLbConfig least_request_lb_config = 37;
-
hasRoundRobinLbConfig
public boolean hasRoundRobinLbConfig()
Optional configuration for the RoundRobin load balancing policy.
.envoy.config.cluster.v3.Cluster.RoundRobinLbConfig round_robin_lb_config = 56;
- Specified by:
hasRoundRobinLbConfig
in interfaceClusterOrBuilder
- Returns:
- Whether the roundRobinLbConfig field is set.
-
getRoundRobinLbConfig
public Cluster.RoundRobinLbConfig getRoundRobinLbConfig()
Optional configuration for the RoundRobin load balancing policy.
.envoy.config.cluster.v3.Cluster.RoundRobinLbConfig round_robin_lb_config = 56;
- Specified by:
getRoundRobinLbConfig
in interfaceClusterOrBuilder
- Returns:
- The roundRobinLbConfig.
-
setRoundRobinLbConfig
public Cluster.Builder setRoundRobinLbConfig(Cluster.RoundRobinLbConfig value)
Optional configuration for the RoundRobin load balancing policy.
.envoy.config.cluster.v3.Cluster.RoundRobinLbConfig round_robin_lb_config = 56;
-
setRoundRobinLbConfig
public Cluster.Builder setRoundRobinLbConfig(Cluster.RoundRobinLbConfig.Builder builderForValue)
Optional configuration for the RoundRobin load balancing policy.
.envoy.config.cluster.v3.Cluster.RoundRobinLbConfig round_robin_lb_config = 56;
-
mergeRoundRobinLbConfig
public Cluster.Builder mergeRoundRobinLbConfig(Cluster.RoundRobinLbConfig value)
Optional configuration for the RoundRobin load balancing policy.
.envoy.config.cluster.v3.Cluster.RoundRobinLbConfig round_robin_lb_config = 56;
-
clearRoundRobinLbConfig
public Cluster.Builder clearRoundRobinLbConfig()
Optional configuration for the RoundRobin load balancing policy.
.envoy.config.cluster.v3.Cluster.RoundRobinLbConfig round_robin_lb_config = 56;
-
getRoundRobinLbConfigBuilder
public Cluster.RoundRobinLbConfig.Builder getRoundRobinLbConfigBuilder()
Optional configuration for the RoundRobin load balancing policy.
.envoy.config.cluster.v3.Cluster.RoundRobinLbConfig round_robin_lb_config = 56;
-
getRoundRobinLbConfigOrBuilder
public Cluster.RoundRobinLbConfigOrBuilder getRoundRobinLbConfigOrBuilder()
Optional configuration for the RoundRobin load balancing policy.
.envoy.config.cluster.v3.Cluster.RoundRobinLbConfig round_robin_lb_config = 56;
- Specified by:
getRoundRobinLbConfigOrBuilder
in interfaceClusterOrBuilder
-
getRoundRobinLbConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Cluster.RoundRobinLbConfig,Cluster.RoundRobinLbConfig.Builder,Cluster.RoundRobinLbConfigOrBuilder> getRoundRobinLbConfigFieldBuilder()
Optional configuration for the RoundRobin load balancing policy.
.envoy.config.cluster.v3.Cluster.RoundRobinLbConfig round_robin_lb_config = 56;
-
hasCommonLbConfig
public boolean hasCommonLbConfig()
Common configuration for all load balancer implementations.
.envoy.config.cluster.v3.Cluster.CommonLbConfig common_lb_config = 27;
- Specified by:
hasCommonLbConfig
in interfaceClusterOrBuilder
- Returns:
- Whether the commonLbConfig field is set.
-
getCommonLbConfig
public Cluster.CommonLbConfig getCommonLbConfig()
Common configuration for all load balancer implementations.
.envoy.config.cluster.v3.Cluster.CommonLbConfig common_lb_config = 27;
- Specified by:
getCommonLbConfig
in interfaceClusterOrBuilder
- Returns:
- The commonLbConfig.
-
setCommonLbConfig
public Cluster.Builder setCommonLbConfig(Cluster.CommonLbConfig value)
Common configuration for all load balancer implementations.
.envoy.config.cluster.v3.Cluster.CommonLbConfig common_lb_config = 27;
-
setCommonLbConfig
public Cluster.Builder setCommonLbConfig(Cluster.CommonLbConfig.Builder builderForValue)
Common configuration for all load balancer implementations.
.envoy.config.cluster.v3.Cluster.CommonLbConfig common_lb_config = 27;
-
mergeCommonLbConfig
public Cluster.Builder mergeCommonLbConfig(Cluster.CommonLbConfig value)
Common configuration for all load balancer implementations.
.envoy.config.cluster.v3.Cluster.CommonLbConfig common_lb_config = 27;
-
clearCommonLbConfig
public Cluster.Builder clearCommonLbConfig()
Common configuration for all load balancer implementations.
.envoy.config.cluster.v3.Cluster.CommonLbConfig common_lb_config = 27;
-
getCommonLbConfigBuilder
public Cluster.CommonLbConfig.Builder getCommonLbConfigBuilder()
Common configuration for all load balancer implementations.
.envoy.config.cluster.v3.Cluster.CommonLbConfig common_lb_config = 27;
-
getCommonLbConfigOrBuilder
public Cluster.CommonLbConfigOrBuilder getCommonLbConfigOrBuilder()
Common configuration for all load balancer implementations.
.envoy.config.cluster.v3.Cluster.CommonLbConfig common_lb_config = 27;
- Specified by:
getCommonLbConfigOrBuilder
in interfaceClusterOrBuilder
-
getCommonLbConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Cluster.CommonLbConfig,Cluster.CommonLbConfig.Builder,Cluster.CommonLbConfigOrBuilder> getCommonLbConfigFieldBuilder()
Common configuration for all load balancer implementations.
.envoy.config.cluster.v3.Cluster.CommonLbConfig common_lb_config = 27;
-
hasTransportSocket
public boolean hasTransportSocket()
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name ``envoy.transport_sockets.tls`` and :ref:`UpstreamTlsContexts <envoy_v3_api_msg_extensions.transport_sockets.tls.v3.UpstreamTlsContext>` in the ``typed_config``. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v3.TransportSocket transport_socket = 24;
- Specified by:
hasTransportSocket
in interfaceClusterOrBuilder
- Returns:
- Whether the transportSocket field is set.
-
getTransportSocket
public TransportSocket getTransportSocket()
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name ``envoy.transport_sockets.tls`` and :ref:`UpstreamTlsContexts <envoy_v3_api_msg_extensions.transport_sockets.tls.v3.UpstreamTlsContext>` in the ``typed_config``. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v3.TransportSocket transport_socket = 24;
- Specified by:
getTransportSocket
in interfaceClusterOrBuilder
- Returns:
- The transportSocket.
-
setTransportSocket
public Cluster.Builder setTransportSocket(TransportSocket value)
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name ``envoy.transport_sockets.tls`` and :ref:`UpstreamTlsContexts <envoy_v3_api_msg_extensions.transport_sockets.tls.v3.UpstreamTlsContext>` in the ``typed_config``. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v3.TransportSocket transport_socket = 24;
-
setTransportSocket
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 ``envoy.transport_sockets.tls`` and :ref:`UpstreamTlsContexts <envoy_v3_api_msg_extensions.transport_sockets.tls.v3.UpstreamTlsContext>` in the ``typed_config``. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v3.TransportSocket transport_socket = 24;
-
mergeTransportSocket
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 ``envoy.transport_sockets.tls`` and :ref:`UpstreamTlsContexts <envoy_v3_api_msg_extensions.transport_sockets.tls.v3.UpstreamTlsContext>` in the ``typed_config``. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v3.TransportSocket transport_socket = 24;
-
clearTransportSocket
public Cluster.Builder clearTransportSocket()
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name ``envoy.transport_sockets.tls`` and :ref:`UpstreamTlsContexts <envoy_v3_api_msg_extensions.transport_sockets.tls.v3.UpstreamTlsContext>` in the ``typed_config``. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v3.TransportSocket transport_socket = 24;
-
getTransportSocketBuilder
public TransportSocket.Builder getTransportSocketBuilder()
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name ``envoy.transport_sockets.tls`` and :ref:`UpstreamTlsContexts <envoy_v3_api_msg_extensions.transport_sockets.tls.v3.UpstreamTlsContext>` in the ``typed_config``. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v3.TransportSocket transport_socket = 24;
-
getTransportSocketOrBuilder
public TransportSocketOrBuilder getTransportSocketOrBuilder()
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name ``envoy.transport_sockets.tls`` and :ref:`UpstreamTlsContexts <envoy_v3_api_msg_extensions.transport_sockets.tls.v3.UpstreamTlsContext>` in the ``typed_config``. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v3.TransportSocket transport_socket = 24;
- Specified by:
getTransportSocketOrBuilder
in interfaceClusterOrBuilder
-
getTransportSocketFieldBuilder
private com.google.protobuf.SingleFieldBuilder<TransportSocket,TransportSocket.Builder,TransportSocketOrBuilder> getTransportSocketFieldBuilder()
Optional custom transport socket implementation to use for upstream connections. To setup TLS, set a transport socket with name ``envoy.transport_sockets.tls`` and :ref:`UpstreamTlsContexts <envoy_v3_api_msg_extensions.transport_sockets.tls.v3.UpstreamTlsContext>` in the ``typed_config``. If no transport socket configuration is specified, new connections will be set up with plaintext.
.envoy.config.core.v3.TransportSocket transport_socket = 24;
-
hasMetadata
public 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.v3.Metadata metadata = 25;
- Specified by:
hasMetadata
in interfaceClusterOrBuilder
- Returns:
- Whether the metadata field is set.
-
getMetadata
public 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.v3.Metadata metadata = 25;
- Specified by:
getMetadata
in interfaceClusterOrBuilder
- Returns:
- The metadata.
-
setMetadata
public 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.v3.Metadata metadata = 25;
-
setMetadata
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.v3.Metadata metadata = 25;
-
mergeMetadata
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.v3.Metadata metadata = 25;
-
clearMetadata
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.v3.Metadata metadata = 25;
-
getMetadataBuilder
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.v3.Metadata metadata = 25;
-
getMetadataOrBuilder
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.v3.Metadata metadata = 25;
- Specified by:
getMetadataOrBuilder
in interfaceClusterOrBuilder
-
getMetadataFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Metadata,Metadata.Builder,MetadataOrBuilder> getMetadataFieldBuilder()
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.v3.Metadata metadata = 25;
-
getProtocolSelectionValue
@Deprecated public int getProtocolSelectionValue()
Deprecated.envoy.config.cluster.v3.Cluster.protocol_selection is deprecated. See envoy/config/cluster/v3/cluster.proto;l=1102Determines how Envoy selects the protocol used to speak to upstream hosts. This has been deprecated in favor of setting explicit protocol selection in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`.
.envoy.config.cluster.v3.Cluster.ClusterProtocolSelection protocol_selection = 26 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getProtocolSelectionValue
in interfaceClusterOrBuilder
- Returns:
- The enum numeric value on the wire for protocolSelection.
-
setProtocolSelectionValue
@Deprecated public Cluster.Builder setProtocolSelectionValue(int value)
Deprecated.envoy.config.cluster.v3.Cluster.protocol_selection is deprecated. See envoy/config/cluster/v3/cluster.proto;l=1102Determines how Envoy selects the protocol used to speak to upstream hosts. This has been deprecated in favor of setting explicit protocol selection in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`.
.envoy.config.cluster.v3.Cluster.ClusterProtocolSelection protocol_selection = 26 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Parameters:
value
- The enum numeric value on the wire for protocolSelection to set.- Returns:
- This builder for chaining.
-
getProtocolSelection
@Deprecated public Cluster.ClusterProtocolSelection getProtocolSelection()
Deprecated.envoy.config.cluster.v3.Cluster.protocol_selection is deprecated. See envoy/config/cluster/v3/cluster.proto;l=1102Determines how Envoy selects the protocol used to speak to upstream hosts. This has been deprecated in favor of setting explicit protocol selection in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`.
.envoy.config.cluster.v3.Cluster.ClusterProtocolSelection protocol_selection = 26 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getProtocolSelection
in interfaceClusterOrBuilder
- Returns:
- The protocolSelection.
-
setProtocolSelection
@Deprecated public Cluster.Builder setProtocolSelection(Cluster.ClusterProtocolSelection value)
Deprecated.envoy.config.cluster.v3.Cluster.protocol_selection is deprecated. See envoy/config/cluster/v3/cluster.proto;l=1102Determines how Envoy selects the protocol used to speak to upstream hosts. This has been deprecated in favor of setting explicit protocol selection in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`.
.envoy.config.cluster.v3.Cluster.ClusterProtocolSelection protocol_selection = 26 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Parameters:
value
- The protocolSelection to set.- Returns:
- This builder for chaining.
-
clearProtocolSelection
@Deprecated public Cluster.Builder clearProtocolSelection()
Deprecated.envoy.config.cluster.v3.Cluster.protocol_selection is deprecated. See envoy/config/cluster/v3/cluster.proto;l=1102Determines how Envoy selects the protocol used to speak to upstream hosts. This has been deprecated in favor of setting explicit protocol selection in the :ref:`http_protocol_options <envoy_v3_api_msg_extensions.upstreams.http.v3.HttpProtocolOptions>` message. http_protocol_options can be set via the cluster's :ref:`extension_protocol_options<envoy_v3_api_field_config.cluster.v3.Cluster.typed_extension_protocol_options>`.
.envoy.config.cluster.v3.Cluster.ClusterProtocolSelection protocol_selection = 26 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Returns:
- This builder for chaining.
-
hasUpstreamConnectionOptions
public boolean hasUpstreamConnectionOptions()
Optional options for upstream connections.
.envoy.config.cluster.v3.UpstreamConnectionOptions upstream_connection_options = 30;
- Specified by:
hasUpstreamConnectionOptions
in interfaceClusterOrBuilder
- Returns:
- Whether the upstreamConnectionOptions field is set.
-
getUpstreamConnectionOptions
public UpstreamConnectionOptions getUpstreamConnectionOptions()
Optional options for upstream connections.
.envoy.config.cluster.v3.UpstreamConnectionOptions upstream_connection_options = 30;
- Specified by:
getUpstreamConnectionOptions
in interfaceClusterOrBuilder
- Returns:
- The upstreamConnectionOptions.
-
setUpstreamConnectionOptions
public Cluster.Builder setUpstreamConnectionOptions(UpstreamConnectionOptions value)
Optional options for upstream connections.
.envoy.config.cluster.v3.UpstreamConnectionOptions upstream_connection_options = 30;
-
setUpstreamConnectionOptions
public Cluster.Builder setUpstreamConnectionOptions(UpstreamConnectionOptions.Builder builderForValue)
Optional options for upstream connections.
.envoy.config.cluster.v3.UpstreamConnectionOptions upstream_connection_options = 30;
-
mergeUpstreamConnectionOptions
public Cluster.Builder mergeUpstreamConnectionOptions(UpstreamConnectionOptions value)
Optional options for upstream connections.
.envoy.config.cluster.v3.UpstreamConnectionOptions upstream_connection_options = 30;
-
clearUpstreamConnectionOptions
public Cluster.Builder clearUpstreamConnectionOptions()
Optional options for upstream connections.
.envoy.config.cluster.v3.UpstreamConnectionOptions upstream_connection_options = 30;
-
getUpstreamConnectionOptionsBuilder
public UpstreamConnectionOptions.Builder getUpstreamConnectionOptionsBuilder()
Optional options for upstream connections.
.envoy.config.cluster.v3.UpstreamConnectionOptions upstream_connection_options = 30;
-
getUpstreamConnectionOptionsOrBuilder
public UpstreamConnectionOptionsOrBuilder getUpstreamConnectionOptionsOrBuilder()
Optional options for upstream connections.
.envoy.config.cluster.v3.UpstreamConnectionOptions upstream_connection_options = 30;
- Specified by:
getUpstreamConnectionOptionsOrBuilder
in interfaceClusterOrBuilder
-
getUpstreamConnectionOptionsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<UpstreamConnectionOptions,UpstreamConnectionOptions.Builder,UpstreamConnectionOptionsOrBuilder> getUpstreamConnectionOptionsFieldBuilder()
Optional options for upstream connections.
.envoy.config.cluster.v3.UpstreamConnectionOptions upstream_connection_options = 30;
-
getCloseConnectionsOnHostHealthFailure
public 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;
- Specified by:
getCloseConnectionsOnHostHealthFailure
in interfaceClusterOrBuilder
- Returns:
- The closeConnectionsOnHostHealthFailure.
-
setCloseConnectionsOnHostHealthFailure
public 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;
- Parameters:
value
- The closeConnectionsOnHostHealthFailure to set.- Returns:
- This builder for chaining.
-
clearCloseConnectionsOnHostHealthFailure
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;
- Returns:
- This builder for chaining.
-
getIgnoreHealthOnHostRemoval
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;
- Specified by:
getIgnoreHealthOnHostRemoval
in interfaceClusterOrBuilder
- Returns:
- The ignoreHealthOnHostRemoval.
-
setIgnoreHealthOnHostRemoval
public 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;
- Parameters:
value
- The ignoreHealthOnHostRemoval to set.- Returns:
- This builder for chaining.
-
clearIgnoreHealthOnHostRemoval
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;
- Returns:
- This builder for chaining.
-
ensureFiltersIsMutable
private void ensureFiltersIsMutable()
-
getFiltersList
public java.util.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.v3.Filter filters = 40;
- Specified by:
getFiltersList
in interfaceClusterOrBuilder
-
getFiltersCount
public 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.v3.Filter filters = 40;
- Specified by:
getFiltersCount
in interfaceClusterOrBuilder
-
getFilters
public 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.v3.Filter filters = 40;
- Specified by:
getFilters
in interfaceClusterOrBuilder
-
setFilters
public 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.v3.Filter filters = 40;
-
setFilters
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.v3.Filter filters = 40;
-
addFilters
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.v3.Filter filters = 40;
-
addFilters
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.v3.Filter filters = 40;
-
addFilters
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.v3.Filter filters = 40;
-
addFilters
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.v3.Filter filters = 40;
-
addAllFilters
public Cluster.Builder addAllFilters(java.lang.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.v3.Filter filters = 40;
-
clearFilters
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.v3.Filter filters = 40;
-
removeFilters
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.v3.Filter filters = 40;
-
getFiltersBuilder
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.v3.Filter filters = 40;
-
getFiltersOrBuilder
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.v3.Filter filters = 40;
- Specified by:
getFiltersOrBuilder
in interfaceClusterOrBuilder
-
getFiltersOrBuilderList
public java.util.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.v3.Filter filters = 40;
- Specified by:
getFiltersOrBuilderList
in interfaceClusterOrBuilder
-
addFiltersBuilder
public 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.v3.Filter filters = 40;
-
addFiltersBuilder
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.v3.Filter filters = 40;
-
getFiltersBuilderList
public java.util.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.v3.Filter filters = 40;
-
getFiltersFieldBuilder
private com.google.protobuf.RepeatedFieldBuilder<Filter,Filter.Builder,FilterOrBuilder> getFiltersFieldBuilder()
-
hasLoadBalancingPolicy
public boolean hasLoadBalancingPolicy()
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.
.envoy.config.cluster.v3.LoadBalancingPolicy load_balancing_policy = 41;
- Specified by:
hasLoadBalancingPolicy
in interfaceClusterOrBuilder
- Returns:
- Whether the loadBalancingPolicy field is set.
-
getLoadBalancingPolicy
public LoadBalancingPolicy getLoadBalancingPolicy()
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.
.envoy.config.cluster.v3.LoadBalancingPolicy load_balancing_policy = 41;
- Specified by:
getLoadBalancingPolicy
in interfaceClusterOrBuilder
- Returns:
- The loadBalancingPolicy.
-
setLoadBalancingPolicy
public Cluster.Builder setLoadBalancingPolicy(LoadBalancingPolicy value)
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.
.envoy.config.cluster.v3.LoadBalancingPolicy load_balancing_policy = 41;
-
setLoadBalancingPolicy
public Cluster.Builder setLoadBalancingPolicy(LoadBalancingPolicy.Builder builderForValue)
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.
.envoy.config.cluster.v3.LoadBalancingPolicy load_balancing_policy = 41;
-
mergeLoadBalancingPolicy
public Cluster.Builder mergeLoadBalancingPolicy(LoadBalancingPolicy value)
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.
.envoy.config.cluster.v3.LoadBalancingPolicy load_balancing_policy = 41;
-
clearLoadBalancingPolicy
public Cluster.Builder clearLoadBalancingPolicy()
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.
.envoy.config.cluster.v3.LoadBalancingPolicy load_balancing_policy = 41;
-
getLoadBalancingPolicyBuilder
public LoadBalancingPolicy.Builder getLoadBalancingPolicyBuilder()
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.
.envoy.config.cluster.v3.LoadBalancingPolicy load_balancing_policy = 41;
-
getLoadBalancingPolicyOrBuilder
public LoadBalancingPolicyOrBuilder getLoadBalancingPolicyOrBuilder()
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.
.envoy.config.cluster.v3.LoadBalancingPolicy load_balancing_policy = 41;
- Specified by:
getLoadBalancingPolicyOrBuilder
in interfaceClusterOrBuilder
-
getLoadBalancingPolicyFieldBuilder
private com.google.protobuf.SingleFieldBuilder<LoadBalancingPolicy,LoadBalancingPolicy.Builder,LoadBalancingPolicyOrBuilder> getLoadBalancingPolicyFieldBuilder()
If this field is set and is supported by the client, it will supersede the value of :ref:`lb_policy<envoy_v3_api_field_config.cluster.v3.Cluster.lb_policy>`.
.envoy.config.cluster.v3.LoadBalancingPolicy load_balancing_policy = 41;
-
hasLrsServer
public 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.v3.ConfigSource lrs_server = 42;
- Specified by:
hasLrsServer
in interfaceClusterOrBuilder
- Returns:
- Whether the lrsServer field is set.
-
getLrsServer
public 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.v3.ConfigSource lrs_server = 42;
- Specified by:
getLrsServer
in interfaceClusterOrBuilder
- Returns:
- The lrsServer.
-
setLrsServer
public 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.v3.ConfigSource lrs_server = 42;
-
setLrsServer
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.v3.ConfigSource lrs_server = 42;
-
mergeLrsServer
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.v3.ConfigSource lrs_server = 42;
-
clearLrsServer
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.v3.ConfigSource lrs_server = 42;
-
getLrsServerBuilder
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.v3.ConfigSource lrs_server = 42;
-
getLrsServerOrBuilder
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.v3.ConfigSource lrs_server = 42;
- Specified by:
getLrsServerOrBuilder
in interfaceClusterOrBuilder
-
getLrsServerFieldBuilder
private com.google.protobuf.SingleFieldBuilder<ConfigSource,ConfigSource.Builder,ConfigSourceOrBuilder> getLrsServerFieldBuilder()
[#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.v3.ConfigSource lrs_server = 42;
-
getTrackTimeoutBudgets
@Deprecated public boolean getTrackTimeoutBudgets()
Deprecated.envoy.config.cluster.v3.Cluster.track_timeout_budgets is deprecated. See envoy/config/cluster/v3/cluster.proto;l=1163If track_timeout_budgets is true, the :ref:`timeout budget histograms <config_cluster_manager_cluster_stats_timeout_budgets>` will be published for each request. These show what percentage of a request's per try and global timeout was used. A value of 0 would indicate that none of the timeout was used or that the timeout was infinite. A value of 100 would indicate that the request took the entirety of the timeout given to it. .. attention:: This field has been deprecated in favor of ``timeout_budgets``, part of :ref:`track_cluster_stats <envoy_v3_api_field_config.cluster.v3.Cluster.track_cluster_stats>`.
bool track_timeout_budgets = 47 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Specified by:
getTrackTimeoutBudgets
in interfaceClusterOrBuilder
- Returns:
- The trackTimeoutBudgets.
-
setTrackTimeoutBudgets
@Deprecated public Cluster.Builder setTrackTimeoutBudgets(boolean value)
Deprecated.envoy.config.cluster.v3.Cluster.track_timeout_budgets is deprecated. See envoy/config/cluster/v3/cluster.proto;l=1163If track_timeout_budgets is true, the :ref:`timeout budget histograms <config_cluster_manager_cluster_stats_timeout_budgets>` will be published for each request. These show what percentage of a request's per try and global timeout was used. A value of 0 would indicate that none of the timeout was used or that the timeout was infinite. A value of 100 would indicate that the request took the entirety of the timeout given to it. .. attention:: This field has been deprecated in favor of ``timeout_budgets``, part of :ref:`track_cluster_stats <envoy_v3_api_field_config.cluster.v3.Cluster.track_cluster_stats>`.
bool track_timeout_budgets = 47 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Parameters:
value
- The trackTimeoutBudgets to set.- Returns:
- This builder for chaining.
-
clearTrackTimeoutBudgets
@Deprecated public Cluster.Builder clearTrackTimeoutBudgets()
Deprecated.envoy.config.cluster.v3.Cluster.track_timeout_budgets is deprecated. See envoy/config/cluster/v3/cluster.proto;l=1163If track_timeout_budgets is true, the :ref:`timeout budget histograms <config_cluster_manager_cluster_stats_timeout_budgets>` will be published for each request. These show what percentage of a request's per try and global timeout was used. A value of 0 would indicate that none of the timeout was used or that the timeout was infinite. A value of 100 would indicate that the request took the entirety of the timeout given to it. .. attention:: This field has been deprecated in favor of ``timeout_budgets``, part of :ref:`track_cluster_stats <envoy_v3_api_field_config.cluster.v3.Cluster.track_cluster_stats>`.
bool track_timeout_budgets = 47 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
- Returns:
- This builder for chaining.
-
hasUpstreamConfig
public 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. [#extension-category: envoy.upstreams]
.envoy.config.core.v3.TypedExtensionConfig upstream_config = 48;
- Specified by:
hasUpstreamConfig
in interfaceClusterOrBuilder
- Returns:
- Whether the upstreamConfig field is set.
-
getUpstreamConfig
public 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. [#extension-category: envoy.upstreams]
.envoy.config.core.v3.TypedExtensionConfig upstream_config = 48;
- Specified by:
getUpstreamConfig
in interfaceClusterOrBuilder
- Returns:
- The upstreamConfig.
-
setUpstreamConfig
public 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. [#extension-category: envoy.upstreams]
.envoy.config.core.v3.TypedExtensionConfig upstream_config = 48;
-
setUpstreamConfig
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. [#extension-category: envoy.upstreams]
.envoy.config.core.v3.TypedExtensionConfig upstream_config = 48;
-
mergeUpstreamConfig
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. [#extension-category: envoy.upstreams]
.envoy.config.core.v3.TypedExtensionConfig upstream_config = 48;
-
clearUpstreamConfig
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. [#extension-category: envoy.upstreams]
.envoy.config.core.v3.TypedExtensionConfig upstream_config = 48;
-
getUpstreamConfigBuilder
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. [#extension-category: envoy.upstreams]
.envoy.config.core.v3.TypedExtensionConfig upstream_config = 48;
-
getUpstreamConfigOrBuilder
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. [#extension-category: envoy.upstreams]
.envoy.config.core.v3.TypedExtensionConfig upstream_config = 48;
- Specified by:
getUpstreamConfigOrBuilder
in interfaceClusterOrBuilder
-
getUpstreamConfigFieldBuilder
private com.google.protobuf.SingleFieldBuilder<TypedExtensionConfig,TypedExtensionConfig.Builder,TypedExtensionConfigOrBuilder> getUpstreamConfigFieldBuilder()
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. [#extension-category: envoy.upstreams]
.envoy.config.core.v3.TypedExtensionConfig upstream_config = 48;
-
hasTrackClusterStats
public boolean hasTrackClusterStats()
Configuration to track optional cluster stats.
.envoy.config.cluster.v3.TrackClusterStats track_cluster_stats = 49;
- Specified by:
hasTrackClusterStats
in interfaceClusterOrBuilder
- Returns:
- Whether the trackClusterStats field is set.
-
getTrackClusterStats
public TrackClusterStats getTrackClusterStats()
Configuration to track optional cluster stats.
.envoy.config.cluster.v3.TrackClusterStats track_cluster_stats = 49;
- Specified by:
getTrackClusterStats
in interfaceClusterOrBuilder
- Returns:
- The trackClusterStats.
-
setTrackClusterStats
public Cluster.Builder setTrackClusterStats(TrackClusterStats value)
Configuration to track optional cluster stats.
.envoy.config.cluster.v3.TrackClusterStats track_cluster_stats = 49;
-
setTrackClusterStats
public Cluster.Builder setTrackClusterStats(TrackClusterStats.Builder builderForValue)
Configuration to track optional cluster stats.
.envoy.config.cluster.v3.TrackClusterStats track_cluster_stats = 49;
-
mergeTrackClusterStats
public Cluster.Builder mergeTrackClusterStats(TrackClusterStats value)
Configuration to track optional cluster stats.
.envoy.config.cluster.v3.TrackClusterStats track_cluster_stats = 49;
-
clearTrackClusterStats
public Cluster.Builder clearTrackClusterStats()
Configuration to track optional cluster stats.
.envoy.config.cluster.v3.TrackClusterStats track_cluster_stats = 49;
-
getTrackClusterStatsBuilder
public TrackClusterStats.Builder getTrackClusterStatsBuilder()
Configuration to track optional cluster stats.
.envoy.config.cluster.v3.TrackClusterStats track_cluster_stats = 49;
-
getTrackClusterStatsOrBuilder
public TrackClusterStatsOrBuilder getTrackClusterStatsOrBuilder()
Configuration to track optional cluster stats.
.envoy.config.cluster.v3.TrackClusterStats track_cluster_stats = 49;
- Specified by:
getTrackClusterStatsOrBuilder
in interfaceClusterOrBuilder
-
getTrackClusterStatsFieldBuilder
private com.google.protobuf.SingleFieldBuilder<TrackClusterStats,TrackClusterStats.Builder,TrackClusterStatsOrBuilder> getTrackClusterStatsFieldBuilder()
Configuration to track optional cluster stats.
.envoy.config.cluster.v3.TrackClusterStats track_cluster_stats = 49;
-
hasPreconnectPolicy
public boolean hasPreconnectPolicy()
Preconnect configuration for this cluster.
.envoy.config.cluster.v3.Cluster.PreconnectPolicy preconnect_policy = 50;
- Specified by:
hasPreconnectPolicy
in interfaceClusterOrBuilder
- Returns:
- Whether the preconnectPolicy field is set.
-
getPreconnectPolicy
public Cluster.PreconnectPolicy getPreconnectPolicy()
Preconnect configuration for this cluster.
.envoy.config.cluster.v3.Cluster.PreconnectPolicy preconnect_policy = 50;
- Specified by:
getPreconnectPolicy
in interfaceClusterOrBuilder
- Returns:
- The preconnectPolicy.
-
setPreconnectPolicy
public Cluster.Builder setPreconnectPolicy(Cluster.PreconnectPolicy value)
Preconnect configuration for this cluster.
.envoy.config.cluster.v3.Cluster.PreconnectPolicy preconnect_policy = 50;
-
setPreconnectPolicy
public Cluster.Builder setPreconnectPolicy(Cluster.PreconnectPolicy.Builder builderForValue)
Preconnect configuration for this cluster.
.envoy.config.cluster.v3.Cluster.PreconnectPolicy preconnect_policy = 50;
-
mergePreconnectPolicy
public Cluster.Builder mergePreconnectPolicy(Cluster.PreconnectPolicy value)
Preconnect configuration for this cluster.
.envoy.config.cluster.v3.Cluster.PreconnectPolicy preconnect_policy = 50;
-
clearPreconnectPolicy
public Cluster.Builder clearPreconnectPolicy()
Preconnect configuration for this cluster.
.envoy.config.cluster.v3.Cluster.PreconnectPolicy preconnect_policy = 50;
-
getPreconnectPolicyBuilder
public Cluster.PreconnectPolicy.Builder getPreconnectPolicyBuilder()
Preconnect configuration for this cluster.
.envoy.config.cluster.v3.Cluster.PreconnectPolicy preconnect_policy = 50;
-
getPreconnectPolicyOrBuilder
public Cluster.PreconnectPolicyOrBuilder getPreconnectPolicyOrBuilder()
Preconnect configuration for this cluster.
.envoy.config.cluster.v3.Cluster.PreconnectPolicy preconnect_policy = 50;
- Specified by:
getPreconnectPolicyOrBuilder
in interfaceClusterOrBuilder
-
getPreconnectPolicyFieldBuilder
private com.google.protobuf.SingleFieldBuilder<Cluster.PreconnectPolicy,Cluster.PreconnectPolicy.Builder,Cluster.PreconnectPolicyOrBuilder> getPreconnectPolicyFieldBuilder()
Preconnect configuration for this cluster.
.envoy.config.cluster.v3.Cluster.PreconnectPolicy preconnect_policy = 50;
-
getConnectionPoolPerDownstreamConnection
public 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;
- Specified by:
getConnectionPoolPerDownstreamConnection
in interfaceClusterOrBuilder
- Returns:
- The connectionPoolPerDownstreamConnection.
-
setConnectionPoolPerDownstreamConnection
public 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;
- Parameters:
value
- The connectionPoolPerDownstreamConnection to set.- Returns:
- This builder for chaining.
-
clearConnectionPoolPerDownstreamConnection
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;
- Returns:
- This builder for chaining.
-
-