From 87ad6dedbee1590335408a6a802ccced31ea31ce Mon Sep 17 00:00:00 2001 From: dpacgdm Date: Wed, 22 Jul 2026 20:53:53 +0530 Subject: [PATCH] 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 --- pkg/healthchecker/types/types.go | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/pkg/healthchecker/types/types.go b/pkg/healthchecker/types/types.go index 20e2d4d9..b08c391e 100644 --- a/pkg/healthchecker/types/types.go +++ b/pkg/healthchecker/types/types.go @@ -82,7 +82,8 @@ func setKubeEndpoints() { kubeletHealthCheckEndpoint = fmt.Sprintf("http://%s/healthz", net.JoinHostPort(hostAddress, kubeletPort)) // 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 - // 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)) }