healthchecker: use kube-proxy /livez to avoid scale-down false alerts

[dpacgdm]

Summary

Cluster Autoscaler marks nodes with ToBeDeletedByClusterAutoscaler during scale-down. kube-proxy /healthz intentionally fails in that case for load-balancer connection draining (KEP-3836), which caused NPD to report kube-proxy as unhealthy and fire unnecessary alerts.

Switch the kube-proxy health check endpoint from /healthz to /livez, which only reflects process health and stays healthy during expected scale-down.

Related issue

#1176

Test plan

• go test ./pkg/healthchecker/... ./cmd/healthchecker/...
• Updated endpoint unit tests to expect /livez for kube-proxy

Made with Cursor

[kubernetes-prow]

Hi @dpacgdm. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dpacgdm
Once this PR has been reviewed and has the lgtm label, please assign wangzhen127 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment