Ubuntu 22.04 LTS – Kubelet node NotReady from cgroup mismatch – 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 stays NotReady and workloads do not schedule.

Environment & Reproduction

Common after runtime or kubelet updates.

Root Cause Analysis

Kubelet and runtime are configured with different cgroup drivers.

Quick Triage

Compare kubelet and containerd cgroup settings.

Step-by-Step Diagnosis

Inspect effective kubelet config and containerd dump.

Solution – Primary Fix

Align both to systemd cgroups and restart services.

Solution – Alternative Approaches

Rejoin node if state is unrecoverable.

Verification & Acceptance Criteria

Node transitions to Ready and pods schedule normally.

Rollback Plan

Restore prior containerd config and restart kubelet.

Prevention & Hardening

Standardize runtime and kubelet configs through automation.

Related Errors & Cross-Refs

Related to swap enabled and CRI endpoint misconfiguration.

Related tutorial: View the step-by-step tutorial for Ubuntu 22.04 LTS.

View all Ubuntu 22.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Ubuntu Kubernetes and container runtime integration docs.