Debian 13 – kubelet Won’t Start Because Swap Is Enabled – Node Recovery

📖 ~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 as kubelet exits on startup checks.

Environment & Reproduction

Occurs on freshly provisioned nodes with default swap configuration.

Root Cause Analysis

kubelet is configured to require swap off under cluster policy.

Quick Triage

Verify active swap devices and kubelet startup flags.

Step-by-Step Diagnosis

Review kubelet journal and static unit overrides.

Solution – Primary Fix

Disable swap immediately and remove swap entries for persistent compliance.

Solution – Alternative Approaches

If swap must remain, explicitly align kubelet feature gates and cluster policy.

Verification & Acceptance Criteria

kubelet stays active and node transitions to Ready state.

Rollback Plan

Re-enable swap only if cluster design allows and capacity planning requires it.

Prevention & Hardening

Bake swap-off defaults into golden images for Kubernetes node pools.

Related Errors & Cross-Refs

Running with swap on is not supported, kubelet failed to run Kubelet.

Related tutorial: View the step-by-step tutorial for Debian 13.

View all Debian 13 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Kubernetes node requirements and Debian kubelet deployment docs.