Replace envoy_reloadable_features_successful_active_health_check_uneject_host with config (#29303)

Signed-off-by: Sunil Narasimhamurthy <sunnrs@amazon.com>

Mirrored from https://github.com/envoyproxy/envoy @ 72f129d273fa32f49581db3abbaf4b62e3e3703c
main
update-envoy[bot] 1 year ago
parent a28b3ea209
commit f1e281c553
  1. 8
      envoy/config/cluster/v3/outlier_detection.proto

@ -19,7 +19,7 @@ option (udpa.annotations.file_status).package_version_status = ACTIVE;
// See the :ref:`architecture overview <arch_overview_outlier_detection>` for
// more information on outlier detection.
// [#next-free-field: 23]
// [#next-free-field: 24]
message OutlierDetection {
option (udpa.annotations.versioning).previous_message_type =
"envoy.api.v2.cluster.OutlierDetection";
@ -161,4 +161,10 @@ message OutlierDetection {
// See :ref:`max_ejection_time_jitter<envoy_v3_api_field_config.cluster.v3.OutlierDetection.base_ejection_time>`
// Defaults to 0s.
google.protobuf.Duration max_ejection_time_jitter = 22;
// If active health checking is enabled and a host is ejected by outlier detection, a successful active health check
// unejects the host by default and considers it as healthy. Unejection also clears all the outlier detection counters.
// To change this default behavior set this config to ``false`` where active health checking will not uneject the host.
// Defaults to true.
google.protobuf.BoolValue successful_active_health_check_uneject_host = 23;
}

Loading…
Cancel
Save