envoyproxy/envoy

Support Degraded Header in Outlier Detection

Open

#40.053 aperta il 27 giu 2025

Vedi su GitHub
 (3 commenti) (0 reazioni) (0 assegnatari)C++ (5373 fork)batch import
area/health_checkingarea/outlier_detectionenhancementhelp wantedno stalebot

Metriche repository

Star
 (27.997 star)
Metriche merge PR
 (Merge medio 8g) (378 PR mergiate in 30 g)

Descrizione

Title: Support Degraded Header in Outlier Detection

Description

Envoy currently allows upstream endpoints to signal a degraded health state via the x-envoy-degraded header during active health checks. However, outlier detection a.k.a passive health checking does not currently interpret this header. If an upstream service returns an HTTP 200 response with x-envoy-degraded: true header, outlier detection still considers this a successful response and does not change the health status of the endpoint.

Request

Extend outlier detection to optionally treat responses containing x-envoy-degraded as a signal to mark the endpoint as degraded, even if the status code is 200. This would allow degraded state signaling to be honored in both active and passive health checks. Specifically, if x-envoy-degraded is observed in a successful response (e.g., HTTP 200), outlier detection marks the endpoint as degraded. This feature could be enabled via a new boolean flag in the outlier detection config.

Guida contributor