Not Able to Clusterize 3 master nodes in microk8s

[Abdulkn]

MicroK8s services (apiserver, kubelet, etcd) not starting on Ubuntu 22.04
I am experiencing an issue where multiple MicroK8s services (apiserver, kubelet, etcd) are not starting on my server. After running systemctl status, I noticed that the services are marked as inactive or dead.

Command outputs:

• snap.microk8s.daemon-etcd.service is inactive (dead).
• snap.microk8s.daemon-kubelet.service and snap.microk8s.daemon-apiserver.service could not be found.

Attempts to restart the services using systemctl restart return an error message saying "Unit [service] not found."

I also tried running sudo microk8s status --wait-ready and restarted MicroK8s using sudo snap restart microk8s, but the issue persists.

My server is running Ubuntu 22.04 and I have installed MicroK8s via snap.

1. Install MicroK8s using sudo snap install microk8s --classic.
2. Run sudo systemctl status snap.microk8s.daemon-apiserver and sudo systemctl status snap.microk8s.daemon-kubelet.
3. Observe that the services are not starting or found.
4. Attempt to restart the services and observe the error message.

Expected Behavior

I expect the MicroK8s services (apiserver, kubelet, etcd) to be running and accessible after installation, and I should be able to restart them without encountering errors.

Actual Behavior

The MicroK8s services are not starting and some services cannot even be found. The services remain in an inactive state or return an error when attempting to restart them.

System Information

• MicroK8s version: v1.25.6
• OS: Ubuntu 22.04 LTS
• Snap version: 2.55.2
• Kernel version: 5.15.0-56-generic

[eaudetcobello]

Hi @Abdulkn,

In recent versions of microk8s the apiserver, controller-manager, kubelet have been wrapped in a service called kubelite (docs). Did you perhaps have an older version of microk8s installed in the past? Maybe the systemd units haven't been properly cleaned up.

Are you encountering any problems with your cluster? Otherwise I would say this is expected behaviour.

[Abdulkn]

Hi @eaudetcobello,
Even the clustering is not possible. Before supplying the joining token, everything is fine, once is supplied, microk8s going down. When i checked with "snap services".. Its showing as api server proxy, etcd, flanneld is inactive.

[Abdulkn]

Even though i have enabled, restarted, nothing is working.. I am stuck in this loop.
I have to clusterise three on prem vms, all 3 are master nodes.