Service snap.microk8s.daemon-kubelite is not running on woker node, resulting in a non-ready node status
Darth-Weider opened this issue · 2 comments
After adding 3 nodes (1 HA node, 2 worker nodes) to an existing HA cluster, the cluster initially functioned as expected. However, following a reboot of all nodes after patching (from v1.29.8 -> 1.29.9), the worker nodes became non-ready. Investigation revealed that the snap.microk8s.daemon-kubelite service was not running on these nodes. Removed 2 worker nodes and add them back as HA nodes, everything just works
Hello @Darth-Weider,
Thank you for raising your issue.
Could you please share the inspection report from your nodes?
Is this issue reproducible with a snap refresh from v1.29.8 to v1.29.9?
With kind regards,
Louise
Unfortunately the inspection report was no longer available (I did a snap remove microk8s before add them back as HA node). I took some screen shots
Not sure if the discrepancy between the older Kubernetes version (v1.29.8) on the datastore master nodes and the newer version (v1.29.9) on the new nodes could be contributing factor to my issue. I have updated my SOP to include patching datastore master nodes to the latest k8s release before adding new nodes to the cluster.