Kubernetes Cluster Node Not Ready
Symptom
The node is not ready after being added to the cluster or is not ready after being restarted.
Key Process and Cause Analysis
The swap in /etc/fstab is commented out but does not take effect.
Conclusion and Solution
Run the systemctl command to disable the swap partition.
- Check the service corresponding to the swap partition.
systemctl | grep swap

- Disable the swap partition.
systemctl mask dev-sda4.swap

- Restart the system.
reboot
Parent topic: Troubleshooting