github/node-problem-detector
1
0
Fork 0
mirror of https://github.com/kubernetes/node-problem-detector.git synced 2026-08-28 01:47:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
1,420 Commits 16 Branches 59 Tags
master
Commit Graph
3 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
dpacgdm 87ad6dedbe 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>
 2026-07-22 20:53:53 +05:30
dpacgdm 43702a7424 config: include --cri-timeout in containerd health-checker defaults 
The health-checker binary honors --cri-timeout when passed via custom
plugin rule args. The default containerd configs omitted the flag, so
crictl used the 2s built-in default. Add --cri-timeout=10s to the
sample Linux and Windows containerd configs.

Signed-off-by: dpacgdm <dpac.gdm@gmail.com>
 2026-07-13 10:44:14 +05:30
dpacgdm 288a3ed68d healthchecker: use kube-proxy /livez to avoid scale-down false alerts 
Cluster Autoscaler marks nodes with ToBeDeletedByClusterAutoscaler during
scale-down. kube-proxy /healthz intentionally fails in that case for LB
connection draining (KEP-3836), which made NPD report kube-proxy as
unhealthy. Switch the kube-proxy probe to /livez, which reflects process
health only.

Signed-off-by: dpacgdm <dpac.gdm@gmail.com>
 2026-07-09 14:28:37 +05:30