healthchecker: clarify kube-proxy /livez comment

/livez still checks process and dataplane sync health; it only excludes
the node-eligibility check used by /healthz for scale-down draining.

Signed-off-by: dpacgdm <dpac.gdm@gmail.com>
This commit is contained in:
dpacgdm
2026-07-22 20:53:53 +05:30
parent 288a3ed68d
commit 87ad6dedbe
+2 -1
View File
@@ -82,7 +82,8 @@ func setKubeEndpoints() {
kubeletHealthCheckEndpoint = fmt.Sprintf("http://%s/healthz", net.JoinHostPort(hostAddress, kubeletPort)) kubeletHealthCheckEndpoint = fmt.Sprintf("http://%s/healthz", net.JoinHostPort(hostAddress, kubeletPort))
// Use /livez for kube-proxy so Cluster Autoscaler scale-down (ToBeDeletedByClusterAutoscaler // Use /livez for kube-proxy so Cluster Autoscaler scale-down (ToBeDeletedByClusterAutoscaler
// taint) does not make NPD report kube-proxy as unhealthy. /healthz intentionally fails in // taint) does not make NPD report kube-proxy as unhealthy. /healthz intentionally fails in
// that case for load-balancer connection draining (KEP-3836); /livez only reflects process health. // that case for load-balancer connection draining (KEP-3836). /livez still checks process and
// dataplane synchronization health; it only excludes the node-eligibility check.
kubeProxyHealthCheckEndpoint = fmt.Sprintf("http://%s/livez", net.JoinHostPort(hostAddress, kubeProxyPort)) kubeProxyHealthCheckEndpoint = fmt.Sprintf("http://%s/livez", net.JoinHostPort(hostAddress, kubeProxyPort))
} }