The /healthz probe fails to function correctly in environments where a proxy is enabled. The issue stems from the probe using the 0.0.0.0 address to test gRPC readiness. This address cannot be effectively filtered using the NO_PROXY setting, resulting in readiness requests to gRPC being routed through the proxy. Consequently, these requests fail because the external proxy attempts to access 127.0.0.1.
Expected Behavior:
The /healthz probe should successfully check the readiness of gRPC services without routing the requests through the proxy. The probe should use an address that can be filtered via the NO_PROXY setting.
Description
The
/healthzprobe fails to function correctly in environments where a proxy is enabled. The issue stems from the probe using the0.0.0.0address to test gRPC readiness. This address cannot be effectively filtered using theNO_PROXYsetting, resulting in readiness requests to gRPC being routed through the proxy. Consequently, these requests fail because the external proxy attempts to access127.0.0.1.Expected Behavior: The
/healthzprobe should successfully check the readiness of gRPC services without routing the requests through the proxy. The probe should use an address that can be filtered via theNO_PROXYsetting.Version 1.4.5