Class Cluster.CommonLbConfig.Builder

  • All Implemented Interfaces:
    com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, Cluster.CommonLbConfigOrBuilder, java.lang.Cloneable
    Enclosing class:
    Cluster.CommonLbConfig

    public static final class Cluster.CommonLbConfig.Builder
    extends com.google.protobuf.GeneratedMessage.Builder<Cluster.CommonLbConfig.Builder>
    implements Cluster.CommonLbConfigOrBuilder
     Common configuration for all load balancer implementations.
     [#next-free-field: 9]
     
    Protobuf type envoy.config.cluster.v3.Cluster.CommonLbConfig
    • Constructor Detail

      • Builder

        private Builder()
      • Builder

        private Builder​(com.google.protobuf.AbstractMessage.BuilderParent parent)
    • Method Detail

      • getDescriptor

        public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
      • internalGetFieldAccessorTable

        protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
        Specified by:
        internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessage.Builder<Cluster.CommonLbConfig.Builder>
      • maybeForceBuilderInitialization

        private void maybeForceBuilderInitialization()
      • clear

        public Cluster.CommonLbConfig.Builder clear()
        Specified by:
        clear in interface com.google.protobuf.Message.Builder
        Specified by:
        clear in interface com.google.protobuf.MessageLite.Builder
        Overrides:
        clear in class com.google.protobuf.GeneratedMessage.Builder<Cluster.CommonLbConfig.Builder>
      • getDescriptorForType

        public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
        Specified by:
        getDescriptorForType in interface com.google.protobuf.Message.Builder
        Specified by:
        getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
        Overrides:
        getDescriptorForType in class com.google.protobuf.GeneratedMessage.Builder<Cluster.CommonLbConfig.Builder>
      • getDefaultInstanceForType

        public Cluster.CommonLbConfig getDefaultInstanceForType()
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder
      • build

        public Cluster.CommonLbConfig build()
        Specified by:
        build in interface com.google.protobuf.Message.Builder
        Specified by:
        build in interface com.google.protobuf.MessageLite.Builder
      • buildPartial

        public Cluster.CommonLbConfig buildPartial()
        Specified by:
        buildPartial in interface com.google.protobuf.Message.Builder
        Specified by:
        buildPartial in interface com.google.protobuf.MessageLite.Builder
      • isInitialized

        public final boolean isInitialized()
        Specified by:
        isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
        Overrides:
        isInitialized in class com.google.protobuf.GeneratedMessage.Builder<Cluster.CommonLbConfig.Builder>
      • mergeFrom

        public Cluster.CommonLbConfig.Builder mergeFrom​(com.google.protobuf.CodedInputStream input,
                                                        com.google.protobuf.ExtensionRegistryLite extensionRegistry)
                                                 throws java.io.IOException
        Specified by:
        mergeFrom in interface com.google.protobuf.Message.Builder
        Specified by:
        mergeFrom in interface com.google.protobuf.MessageLite.Builder
        Overrides:
        mergeFrom in class com.google.protobuf.AbstractMessage.Builder<Cluster.CommonLbConfig.Builder>
        Throws:
        java.io.IOException
      • hasHealthyPanicThreshold

        public boolean hasHealthyPanicThreshold()
         Configures the :ref:`healthy panic threshold <arch_overview_load_balancing_panic_threshold>`.
         If not specified, the default is 50%.
         To disable panic mode, set to 0%.
        
         .. note::
         The specified percent will be truncated to the nearest 1%.
         
        .envoy.type.v3.Percent healthy_panic_threshold = 1;
        Specified by:
        hasHealthyPanicThreshold in interface Cluster.CommonLbConfigOrBuilder
        Returns:
        Whether the healthyPanicThreshold field is set.
      • getHealthyPanicThreshold

        public Percent getHealthyPanicThreshold()
         Configures the :ref:`healthy panic threshold <arch_overview_load_balancing_panic_threshold>`.
         If not specified, the default is 50%.
         To disable panic mode, set to 0%.
        
         .. note::
         The specified percent will be truncated to the nearest 1%.
         
        .envoy.type.v3.Percent healthy_panic_threshold = 1;
        Specified by:
        getHealthyPanicThreshold in interface Cluster.CommonLbConfigOrBuilder
        Returns:
        The healthyPanicThreshold.
      • setHealthyPanicThreshold

        public Cluster.CommonLbConfig.Builder setHealthyPanicThreshold​(Percent value)
         Configures the :ref:`healthy panic threshold <arch_overview_load_balancing_panic_threshold>`.
         If not specified, the default is 50%.
         To disable panic mode, set to 0%.
        
         .. note::
         The specified percent will be truncated to the nearest 1%.
         
        .envoy.type.v3.Percent healthy_panic_threshold = 1;
      • setHealthyPanicThreshold

        public Cluster.CommonLbConfig.Builder setHealthyPanicThreshold​(Percent.Builder builderForValue)
         Configures the :ref:`healthy panic threshold <arch_overview_load_balancing_panic_threshold>`.
         If not specified, the default is 50%.
         To disable panic mode, set to 0%.
        
         .. note::
         The specified percent will be truncated to the nearest 1%.
         
        .envoy.type.v3.Percent healthy_panic_threshold = 1;
      • mergeHealthyPanicThreshold

        public Cluster.CommonLbConfig.Builder mergeHealthyPanicThreshold​(Percent value)
         Configures the :ref:`healthy panic threshold <arch_overview_load_balancing_panic_threshold>`.
         If not specified, the default is 50%.
         To disable panic mode, set to 0%.
        
         .. note::
         The specified percent will be truncated to the nearest 1%.
         
        .envoy.type.v3.Percent healthy_panic_threshold = 1;
      • clearHealthyPanicThreshold

        public Cluster.CommonLbConfig.Builder clearHealthyPanicThreshold()
         Configures the :ref:`healthy panic threshold <arch_overview_load_balancing_panic_threshold>`.
         If not specified, the default is 50%.
         To disable panic mode, set to 0%.
        
         .. note::
         The specified percent will be truncated to the nearest 1%.
         
        .envoy.type.v3.Percent healthy_panic_threshold = 1;
      • getHealthyPanicThresholdBuilder

        public Percent.Builder getHealthyPanicThresholdBuilder()
         Configures the :ref:`healthy panic threshold <arch_overview_load_balancing_panic_threshold>`.
         If not specified, the default is 50%.
         To disable panic mode, set to 0%.
        
         .. note::
         The specified percent will be truncated to the nearest 1%.
         
        .envoy.type.v3.Percent healthy_panic_threshold = 1;
      • getHealthyPanicThresholdOrBuilder

        public PercentOrBuilder getHealthyPanicThresholdOrBuilder()
         Configures the :ref:`healthy panic threshold <arch_overview_load_balancing_panic_threshold>`.
         If not specified, the default is 50%.
         To disable panic mode, set to 0%.
        
         .. note::
         The specified percent will be truncated to the nearest 1%.
         
        .envoy.type.v3.Percent healthy_panic_threshold = 1;
        Specified by:
        getHealthyPanicThresholdOrBuilder in interface Cluster.CommonLbConfigOrBuilder
      • getHealthyPanicThresholdFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<Percent,​Percent.Builder,​PercentOrBuilder> getHealthyPanicThresholdFieldBuilder()
         Configures the :ref:`healthy panic threshold <arch_overview_load_balancing_panic_threshold>`.
         If not specified, the default is 50%.
         To disable panic mode, set to 0%.
        
         .. note::
         The specified percent will be truncated to the nearest 1%.
         
        .envoy.type.v3.Percent healthy_panic_threshold = 1;
      • hasZoneAwareLbConfig

        public boolean hasZoneAwareLbConfig()
        .envoy.config.cluster.v3.Cluster.CommonLbConfig.ZoneAwareLbConfig zone_aware_lb_config = 2;
        Specified by:
        hasZoneAwareLbConfig in interface Cluster.CommonLbConfigOrBuilder
        Returns:
        Whether the zoneAwareLbConfig field is set.
      • clearZoneAwareLbConfig

        public Cluster.CommonLbConfig.Builder clearZoneAwareLbConfig()
        .envoy.config.cluster.v3.Cluster.CommonLbConfig.ZoneAwareLbConfig zone_aware_lb_config = 2;
      • hasLocalityWeightedLbConfig

        public boolean hasLocalityWeightedLbConfig()
        .envoy.config.cluster.v3.Cluster.CommonLbConfig.LocalityWeightedLbConfig locality_weighted_lb_config = 3;
        Specified by:
        hasLocalityWeightedLbConfig in interface Cluster.CommonLbConfigOrBuilder
        Returns:
        Whether the localityWeightedLbConfig field is set.
      • clearLocalityWeightedLbConfig

        public Cluster.CommonLbConfig.Builder clearLocalityWeightedLbConfig()
        .envoy.config.cluster.v3.Cluster.CommonLbConfig.LocalityWeightedLbConfig locality_weighted_lb_config = 3;
      • hasUpdateMergeWindow

        public boolean hasUpdateMergeWindow()
         If set, all health check/weight/metadata updates that happen within this duration will be
         merged and delivered in one shot when the duration expires. The start of the duration is when
         the first update happens. This is useful for big clusters, with potentially noisy deploys
         that might trigger excessive CPU usage due to a constant stream of healthcheck state changes
         or metadata updates. The first set of updates to be seen apply immediately (e.g.: a new
         cluster). Please always keep in mind that the use of sandbox technologies may change this
         behavior.
        
         If this is not set, we default to a merge window of 1000ms. To disable it, set the merge
         window to 0.
        
         Note: merging does not apply to cluster membership changes (e.g.: adds/removes); this is
         because merging those updates isn't currently safe. See
         https://github.com/envoyproxy/envoy/pull/3941.
         
        .google.protobuf.Duration update_merge_window = 4;
        Specified by:
        hasUpdateMergeWindow in interface Cluster.CommonLbConfigOrBuilder
        Returns:
        Whether the updateMergeWindow field is set.
      • getUpdateMergeWindow

        public com.google.protobuf.Duration getUpdateMergeWindow()
         If set, all health check/weight/metadata updates that happen within this duration will be
         merged and delivered in one shot when the duration expires. The start of the duration is when
         the first update happens. This is useful for big clusters, with potentially noisy deploys
         that might trigger excessive CPU usage due to a constant stream of healthcheck state changes
         or metadata updates. The first set of updates to be seen apply immediately (e.g.: a new
         cluster). Please always keep in mind that the use of sandbox technologies may change this
         behavior.
        
         If this is not set, we default to a merge window of 1000ms. To disable it, set the merge
         window to 0.
        
         Note: merging does not apply to cluster membership changes (e.g.: adds/removes); this is
         because merging those updates isn't currently safe. See
         https://github.com/envoyproxy/envoy/pull/3941.
         
        .google.protobuf.Duration update_merge_window = 4;
        Specified by:
        getUpdateMergeWindow in interface Cluster.CommonLbConfigOrBuilder
        Returns:
        The updateMergeWindow.
      • setUpdateMergeWindow

        public Cluster.CommonLbConfig.Builder setUpdateMergeWindow​(com.google.protobuf.Duration value)
         If set, all health check/weight/metadata updates that happen within this duration will be
         merged and delivered in one shot when the duration expires. The start of the duration is when
         the first update happens. This is useful for big clusters, with potentially noisy deploys
         that might trigger excessive CPU usage due to a constant stream of healthcheck state changes
         or metadata updates. The first set of updates to be seen apply immediately (e.g.: a new
         cluster). Please always keep in mind that the use of sandbox technologies may change this
         behavior.
        
         If this is not set, we default to a merge window of 1000ms. To disable it, set the merge
         window to 0.
        
         Note: merging does not apply to cluster membership changes (e.g.: adds/removes); this is
         because merging those updates isn't currently safe. See
         https://github.com/envoyproxy/envoy/pull/3941.
         
        .google.protobuf.Duration update_merge_window = 4;
      • setUpdateMergeWindow

        public Cluster.CommonLbConfig.Builder setUpdateMergeWindow​(com.google.protobuf.Duration.Builder builderForValue)
         If set, all health check/weight/metadata updates that happen within this duration will be
         merged and delivered in one shot when the duration expires. The start of the duration is when
         the first update happens. This is useful for big clusters, with potentially noisy deploys
         that might trigger excessive CPU usage due to a constant stream of healthcheck state changes
         or metadata updates. The first set of updates to be seen apply immediately (e.g.: a new
         cluster). Please always keep in mind that the use of sandbox technologies may change this
         behavior.
        
         If this is not set, we default to a merge window of 1000ms. To disable it, set the merge
         window to 0.
        
         Note: merging does not apply to cluster membership changes (e.g.: adds/removes); this is
         because merging those updates isn't currently safe. See
         https://github.com/envoyproxy/envoy/pull/3941.
         
        .google.protobuf.Duration update_merge_window = 4;
      • mergeUpdateMergeWindow

        public Cluster.CommonLbConfig.Builder mergeUpdateMergeWindow​(com.google.protobuf.Duration value)
         If set, all health check/weight/metadata updates that happen within this duration will be
         merged and delivered in one shot when the duration expires. The start of the duration is when
         the first update happens. This is useful for big clusters, with potentially noisy deploys
         that might trigger excessive CPU usage due to a constant stream of healthcheck state changes
         or metadata updates. The first set of updates to be seen apply immediately (e.g.: a new
         cluster). Please always keep in mind that the use of sandbox technologies may change this
         behavior.
        
         If this is not set, we default to a merge window of 1000ms. To disable it, set the merge
         window to 0.
        
         Note: merging does not apply to cluster membership changes (e.g.: adds/removes); this is
         because merging those updates isn't currently safe. See
         https://github.com/envoyproxy/envoy/pull/3941.
         
        .google.protobuf.Duration update_merge_window = 4;
      • clearUpdateMergeWindow

        public Cluster.CommonLbConfig.Builder clearUpdateMergeWindow()
         If set, all health check/weight/metadata updates that happen within this duration will be
         merged and delivered in one shot when the duration expires. The start of the duration is when
         the first update happens. This is useful for big clusters, with potentially noisy deploys
         that might trigger excessive CPU usage due to a constant stream of healthcheck state changes
         or metadata updates. The first set of updates to be seen apply immediately (e.g.: a new
         cluster). Please always keep in mind that the use of sandbox technologies may change this
         behavior.
        
         If this is not set, we default to a merge window of 1000ms. To disable it, set the merge
         window to 0.
        
         Note: merging does not apply to cluster membership changes (e.g.: adds/removes); this is
         because merging those updates isn't currently safe. See
         https://github.com/envoyproxy/envoy/pull/3941.
         
        .google.protobuf.Duration update_merge_window = 4;
      • getUpdateMergeWindowBuilder

        public com.google.protobuf.Duration.Builder getUpdateMergeWindowBuilder()
         If set, all health check/weight/metadata updates that happen within this duration will be
         merged and delivered in one shot when the duration expires. The start of the duration is when
         the first update happens. This is useful for big clusters, with potentially noisy deploys
         that might trigger excessive CPU usage due to a constant stream of healthcheck state changes
         or metadata updates. The first set of updates to be seen apply immediately (e.g.: a new
         cluster). Please always keep in mind that the use of sandbox technologies may change this
         behavior.
        
         If this is not set, we default to a merge window of 1000ms. To disable it, set the merge
         window to 0.
        
         Note: merging does not apply to cluster membership changes (e.g.: adds/removes); this is
         because merging those updates isn't currently safe. See
         https://github.com/envoyproxy/envoy/pull/3941.
         
        .google.protobuf.Duration update_merge_window = 4;
      • getUpdateMergeWindowOrBuilder

        public com.google.protobuf.DurationOrBuilder getUpdateMergeWindowOrBuilder()
         If set, all health check/weight/metadata updates that happen within this duration will be
         merged and delivered in one shot when the duration expires. The start of the duration is when
         the first update happens. This is useful for big clusters, with potentially noisy deploys
         that might trigger excessive CPU usage due to a constant stream of healthcheck state changes
         or metadata updates. The first set of updates to be seen apply immediately (e.g.: a new
         cluster). Please always keep in mind that the use of sandbox technologies may change this
         behavior.
        
         If this is not set, we default to a merge window of 1000ms. To disable it, set the merge
         window to 0.
        
         Note: merging does not apply to cluster membership changes (e.g.: adds/removes); this is
         because merging those updates isn't currently safe. See
         https://github.com/envoyproxy/envoy/pull/3941.
         
        .google.protobuf.Duration update_merge_window = 4;
        Specified by:
        getUpdateMergeWindowOrBuilder in interface Cluster.CommonLbConfigOrBuilder
      • getUpdateMergeWindowFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<com.google.protobuf.Duration,​com.google.protobuf.Duration.Builder,​com.google.protobuf.DurationOrBuilder> getUpdateMergeWindowFieldBuilder()
         If set, all health check/weight/metadata updates that happen within this duration will be
         merged and delivered in one shot when the duration expires. The start of the duration is when
         the first update happens. This is useful for big clusters, with potentially noisy deploys
         that might trigger excessive CPU usage due to a constant stream of healthcheck state changes
         or metadata updates. The first set of updates to be seen apply immediately (e.g.: a new
         cluster). Please always keep in mind that the use of sandbox technologies may change this
         behavior.
        
         If this is not set, we default to a merge window of 1000ms. To disable it, set the merge
         window to 0.
        
         Note: merging does not apply to cluster membership changes (e.g.: adds/removes); this is
         because merging those updates isn't currently safe. See
         https://github.com/envoyproxy/envoy/pull/3941.
         
        .google.protobuf.Duration update_merge_window = 4;
      • getIgnoreNewHostsUntilFirstHc

        public boolean getIgnoreNewHostsUntilFirstHc()
         If set to true, Envoy will :ref:`exclude <arch_overview_load_balancing_excluded>` new hosts
         when computing load balancing weights until they have been health checked for the first time.
         This will have no effect unless active health checking is also configured.
         
        bool ignore_new_hosts_until_first_hc = 5;
        Specified by:
        getIgnoreNewHostsUntilFirstHc in interface Cluster.CommonLbConfigOrBuilder
        Returns:
        The ignoreNewHostsUntilFirstHc.
      • setIgnoreNewHostsUntilFirstHc

        public Cluster.CommonLbConfig.Builder setIgnoreNewHostsUntilFirstHc​(boolean value)
         If set to true, Envoy will :ref:`exclude <arch_overview_load_balancing_excluded>` new hosts
         when computing load balancing weights until they have been health checked for the first time.
         This will have no effect unless active health checking is also configured.
         
        bool ignore_new_hosts_until_first_hc = 5;
        Parameters:
        value - The ignoreNewHostsUntilFirstHc to set.
        Returns:
        This builder for chaining.
      • clearIgnoreNewHostsUntilFirstHc

        public Cluster.CommonLbConfig.Builder clearIgnoreNewHostsUntilFirstHc()
         If set to true, Envoy will :ref:`exclude <arch_overview_load_balancing_excluded>` new hosts
         when computing load balancing weights until they have been health checked for the first time.
         This will have no effect unless active health checking is also configured.
         
        bool ignore_new_hosts_until_first_hc = 5;
        Returns:
        This builder for chaining.
      • getCloseConnectionsOnHostSetChange

        public boolean getCloseConnectionsOnHostSetChange()
         If set to ``true``, the cluster manager will drain all existing
         connections to upstream hosts whenever hosts are added or removed from the cluster.
         
        bool close_connections_on_host_set_change = 6;
        Specified by:
        getCloseConnectionsOnHostSetChange in interface Cluster.CommonLbConfigOrBuilder
        Returns:
        The closeConnectionsOnHostSetChange.
      • setCloseConnectionsOnHostSetChange

        public Cluster.CommonLbConfig.Builder setCloseConnectionsOnHostSetChange​(boolean value)
         If set to ``true``, the cluster manager will drain all existing
         connections to upstream hosts whenever hosts are added or removed from the cluster.
         
        bool close_connections_on_host_set_change = 6;
        Parameters:
        value - The closeConnectionsOnHostSetChange to set.
        Returns:
        This builder for chaining.
      • clearCloseConnectionsOnHostSetChange

        public Cluster.CommonLbConfig.Builder clearCloseConnectionsOnHostSetChange()
         If set to ``true``, the cluster manager will drain all existing
         connections to upstream hosts whenever hosts are added or removed from the cluster.
         
        bool close_connections_on_host_set_change = 6;
        Returns:
        This builder for chaining.
      • hasConsistentHashingLbConfig

        public boolean hasConsistentHashingLbConfig()
         Common Configuration for all consistent hashing load balancers (MaglevLb, RingHashLb, etc.)
         
        .envoy.config.cluster.v3.Cluster.CommonLbConfig.ConsistentHashingLbConfig consistent_hashing_lb_config = 7;
        Specified by:
        hasConsistentHashingLbConfig in interface Cluster.CommonLbConfigOrBuilder
        Returns:
        Whether the consistentHashingLbConfig field is set.
      • clearConsistentHashingLbConfig

        public Cluster.CommonLbConfig.Builder clearConsistentHashingLbConfig()
         Common Configuration for all consistent hashing load balancers (MaglevLb, RingHashLb, etc.)
         
        .envoy.config.cluster.v3.Cluster.CommonLbConfig.ConsistentHashingLbConfig consistent_hashing_lb_config = 7;
      • getConsistentHashingLbConfigBuilder

        public Cluster.CommonLbConfig.ConsistentHashingLbConfig.Builder getConsistentHashingLbConfigBuilder()
         Common Configuration for all consistent hashing load balancers (MaglevLb, RingHashLb, etc.)
         
        .envoy.config.cluster.v3.Cluster.CommonLbConfig.ConsistentHashingLbConfig consistent_hashing_lb_config = 7;
      • hasOverrideHostStatus

        public boolean hasOverrideHostStatus()
         This controls what hosts are considered valid when using
         :ref:`host overrides <arch_overview_load_balancing_override_host>`, which is used by some
         filters to modify the load balancing decision.
        
         If this is unset then [UNKNOWN, HEALTHY, DEGRADED] will be applied by default. If this is
         set with an empty set of statuses then host overrides will be ignored by the load balancing.
         
        .envoy.config.core.v3.HealthStatusSet override_host_status = 8;
        Specified by:
        hasOverrideHostStatus in interface Cluster.CommonLbConfigOrBuilder
        Returns:
        Whether the overrideHostStatus field is set.
      • getOverrideHostStatus

        public HealthStatusSet getOverrideHostStatus()
         This controls what hosts are considered valid when using
         :ref:`host overrides <arch_overview_load_balancing_override_host>`, which is used by some
         filters to modify the load balancing decision.
        
         If this is unset then [UNKNOWN, HEALTHY, DEGRADED] will be applied by default. If this is
         set with an empty set of statuses then host overrides will be ignored by the load balancing.
         
        .envoy.config.core.v3.HealthStatusSet override_host_status = 8;
        Specified by:
        getOverrideHostStatus in interface Cluster.CommonLbConfigOrBuilder
        Returns:
        The overrideHostStatus.
      • setOverrideHostStatus

        public Cluster.CommonLbConfig.Builder setOverrideHostStatus​(HealthStatusSet value)
         This controls what hosts are considered valid when using
         :ref:`host overrides <arch_overview_load_balancing_override_host>`, which is used by some
         filters to modify the load balancing decision.
        
         If this is unset then [UNKNOWN, HEALTHY, DEGRADED] will be applied by default. If this is
         set with an empty set of statuses then host overrides will be ignored by the load balancing.
         
        .envoy.config.core.v3.HealthStatusSet override_host_status = 8;
      • setOverrideHostStatus

        public Cluster.CommonLbConfig.Builder setOverrideHostStatus​(HealthStatusSet.Builder builderForValue)
         This controls what hosts are considered valid when using
         :ref:`host overrides <arch_overview_load_balancing_override_host>`, which is used by some
         filters to modify the load balancing decision.
        
         If this is unset then [UNKNOWN, HEALTHY, DEGRADED] will be applied by default. If this is
         set with an empty set of statuses then host overrides will be ignored by the load balancing.
         
        .envoy.config.core.v3.HealthStatusSet override_host_status = 8;
      • mergeOverrideHostStatus

        public Cluster.CommonLbConfig.Builder mergeOverrideHostStatus​(HealthStatusSet value)
         This controls what hosts are considered valid when using
         :ref:`host overrides <arch_overview_load_balancing_override_host>`, which is used by some
         filters to modify the load balancing decision.
        
         If this is unset then [UNKNOWN, HEALTHY, DEGRADED] will be applied by default. If this is
         set with an empty set of statuses then host overrides will be ignored by the load balancing.
         
        .envoy.config.core.v3.HealthStatusSet override_host_status = 8;
      • clearOverrideHostStatus

        public Cluster.CommonLbConfig.Builder clearOverrideHostStatus()
         This controls what hosts are considered valid when using
         :ref:`host overrides <arch_overview_load_balancing_override_host>`, which is used by some
         filters to modify the load balancing decision.
        
         If this is unset then [UNKNOWN, HEALTHY, DEGRADED] will be applied by default. If this is
         set with an empty set of statuses then host overrides will be ignored by the load balancing.
         
        .envoy.config.core.v3.HealthStatusSet override_host_status = 8;
      • getOverrideHostStatusBuilder

        public HealthStatusSet.Builder getOverrideHostStatusBuilder()
         This controls what hosts are considered valid when using
         :ref:`host overrides <arch_overview_load_balancing_override_host>`, which is used by some
         filters to modify the load balancing decision.
        
         If this is unset then [UNKNOWN, HEALTHY, DEGRADED] will be applied by default. If this is
         set with an empty set of statuses then host overrides will be ignored by the load balancing.
         
        .envoy.config.core.v3.HealthStatusSet override_host_status = 8;
      • getOverrideHostStatusOrBuilder

        public HealthStatusSetOrBuilder getOverrideHostStatusOrBuilder()
         This controls what hosts are considered valid when using
         :ref:`host overrides <arch_overview_load_balancing_override_host>`, which is used by some
         filters to modify the load balancing decision.
        
         If this is unset then [UNKNOWN, HEALTHY, DEGRADED] will be applied by default. If this is
         set with an empty set of statuses then host overrides will be ignored by the load balancing.
         
        .envoy.config.core.v3.HealthStatusSet override_host_status = 8;
        Specified by:
        getOverrideHostStatusOrBuilder in interface Cluster.CommonLbConfigOrBuilder
      • getOverrideHostStatusFieldBuilder

        private com.google.protobuf.SingleFieldBuilder<HealthStatusSet,​HealthStatusSet.Builder,​HealthStatusSetOrBuilder> getOverrideHostStatusFieldBuilder()
         This controls what hosts are considered valid when using
         :ref:`host overrides <arch_overview_load_balancing_override_host>`, which is used by some
         filters to modify the load balancing decision.
        
         If this is unset then [UNKNOWN, HEALTHY, DEGRADED] will be applied by default. If this is
         set with an empty set of statuses then host overrides will be ignored by the load balancing.
         
        .envoy.config.core.v3.HealthStatusSet override_host_status = 8;