Self-healing Clusters: Game of Nodes and the Scaling Throne
summary
Shows a live demo wiring Node Problem Detector, descheduler, and cluster autoscaler so pending pods trigger a new node, the descheduler rebalances by evicting duplicates, and a tainted node forces eviction. Shows NPD creating node taints for memory/pressure, descheduler configured via a ConfigMap with low/high utilization and remove-duplicate policies, and VPA in recommendation mode to surface resource requests. Useful if wanting concrete install and config steps that actually work on GKE.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:14Self-healing clusters in Kubernetes
- 4:09Kubernetes stability challenges
- 9:46Resilient cluster building blocks
- 13:39Node Problem Detector
- 15:30Descheduler policies
- 18:23Cluster Autoscaler
- 21:54Live demo: Self-healing tools
- 30:34Key takeaways
- 32:20Q&A
related talks
01h 01mKubernetes – going beyond the basics
50mKubernetes - going beyond the basics
29mProactive cluster autoscaling in Kubernetes
59mKubernetes - going beyond the basics
28mThe Magic of Kubernetes Self-Healing Capabilities
21mSelf-Healing Kubernetes
29mProactive cluster autoscaling in Kubernetes
37mAuto-scaling party:VPA, HPA, KEDA, nodes, how do they dance?-Nic Vermande & Oluebube Princess Egbuna
