Debian 12 – kubelet fails with swap enabled and node stays NotReady – Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Node remains NotReady and workloads fail to schedule or restart correctly.

Environment & Reproduction

Typical on newly provisioned Debian 12 workers where swap remains active by default.

Root Cause Analysis

kubelet startup validation rejects active swap unless explicit swap support policy is configured.

Quick Triage

Check kubelet logs, swap state, and node conditions from control plane.

Step-by-Step Diagnosis

Run: sudo swapon –show; free -h; sudo journalctl -u kubelet -n 200 –no-pager; kubectl describe node | egrep -i ‘Ready|MemoryPressure|Kubelet’.

Solution – Primary Fix

Disable swap with sudo swapoff -a; comment swap lines in /etc/fstab; restart kubelet: sudo systemctl restart kubelet.

Solution – Alternative Approaches

If swap is required, configure Kubernetes feature gates and policies explicitly for that design.

Verification & Acceptance Criteria

Node transitions to Ready and pods schedule without kubelet swap-related errors.

Rollback Plan

Re-enable swap and revert kubelet flags only if cluster policy supports managed swap usage.

Prevention & Hardening

Enforce swap-off baseline in node bootstrap scripts and compliance checks.

Related Errors & Cross-Refs

Related to container runtime startup failures and cgroup memory accounting misconfiguration.

Related tutorial: View the step-by-step tutorial for debian-12.

View all debian-12 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Kubernetes kubeadm prerequisites and Debian node hardening guidance.