A dead Kubernetes node is detected in 3 seconds and keeps receiving traffic for 13

DEV Community·15 points·remdore·about 11 hours ago·dev.to

The 40-second node-monitor-grace-period everyone quotes is not what happens. I hard-killed a node ten times and measured where the failures actually live, then got the fix wrong and had to say so.

Read the full article at dev.to →

#kubernetes #node #detected #receiving #traffic #dead #dead kubernetes #kubernetes node

Related stories

FAA tees up $875M AI tool to help manage air traffic congestionarstechnica.com
Ars Technica · 0 points · 14 days ago
KubeSolo – Ultra-lightweight, single-node Kubernetes from Portainerkubesolo.io
Hacker News · 1 points · 9 days ago
Ask HN: Why so many dead comments lately?
Hacker News · 11 points · 9 days ago
Kubernetes 1.37's kyaml output closes a YAML bug that still deletes data on applydev.to
DEV Community · 7 points · 8 days ago
Show HN: A benchmark comparison of C++ vs. Node.js performancevikky2810.github.io
Hacker News · 5 points · 8 days ago
Bad bot traffic is growing 9 times faster than human web trafficfastcompany.com
Hacker News · 2 points · 9 days ago

Related topics

devops57 docker34 still111 community42 portainer3 security314 node32 zero downtime3 secure36 hands22 scheduling3 early33