Under the hood: how Amazon EKS Auto Mode detects, repairs, and diagnoses node failures

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

A GPU drops off the PCIe bus, a network interface goes dark, or the container runtime wedges. On most Kubernetes clusters, that is the start of a pager story: someone wakes up, reads dashboards, SSHes in, cordons, drains, and terminates the instance by hand. With Amazon Elastic Kubernetes Service (Amazon EKS) Auto Mode, the failing node is detected, drained, and replaced automatically before anyone reaches for a laptop. Two components work together to make this happen. The Amazon EKS Node Monitoring Agent (NMA) detects the fault and records it as a Kubernetes node condition. Karpenter reads that condition and replaces the node. On EKS Auto Mode, both run automatically with no configuration. On other EKS compute (managed node groups or self-managed Karpenter), you can install the Node Monitoring Agent as an EKS add-on to get the same detection signals. This gives you the same repair behavior. The difference on Auto Mode is that the agent runs as a systemd service baked into the AMI rather than a DaemonSet. That means it keeps running even when pod scheduling is degraded and cannot be accidentally evicted or misconfigured. In this post, we show how the repair cycle works step by step and why specific faults trigger node replacement while others stay informational. We also explain how the safety thresholds prevent cascading failures and how you collect diagnostics from any node without ever logging in. How detection and repair work together The cycle has two halves, and a clean contract between them. Detection: the Node Monitoring Agent. The agent watches the kernel, the …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://aws.amazon.com/blogs/containers/under-the-hood-how-amazon-eks-auto-mode-detects-repairs-and-diagnoses-node-failures/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.