macOS HA Node does not complete joining cluster

[mlb5000]

Summary

I have a 5 node microk8s cluster in HA mode that is composed wholly of Ubuntu instances. I wanted to add macOS nodes to the existing cluster.

1. I run microk8s add-node on one of the existing nodes.
2. I then run the generated command inside the microk8s multipass VM running on the macOS node.

ubuntu@microk8s-vm:~$ microk8s join 192.168.2.5:25000/{stuff}/{other_stuff}
Contacting cluster at 192.168.2.5
Waiting for this node to finish joining the cluster. .. .. ..
ubuntu@microk8s-vm:~$ kubectl get pods
E0220 11:56:44.849246   26848 memcache.go:255] couldn't get resource list for metrics.k8s.io/v1beta1: client rate limiter Wait returned an error: context deadline exceeded - error from a previous attempt: unexpected EOF
.
continues to successfully display all of the pods in the cluster

3. Run kubectl get nodes. The microk8s-vm node does not exist in the list.
4. I checked dqlite, and the microk8s-vm node's IP address does exist in there.
5. microk8s inspect does not report any errors (says the services are running)
6. microk8s status reports that microk8s is not running...

ubuntu@microk8s-vm:~$ microk8s inspect
Inspecting system
Inspecting Certificates
Inspecting services
  Service snap.microk8s.daemon-cluster-agent is running
  Service snap.microk8s.daemon-containerd is running
  Service snap.microk8s.daemon-kubelite is running
  Service snap.microk8s.daemon-k8s-dqlite is running
  Service snap.microk8s.daemon-apiserver-kicker is running
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
  Copy processes list to the final report tarball
  Copy disk usage information to the final report tarball
  Copy memory usage information to the final report tarball
  Copy server uptime to the final report tarball
  Copy openSSL information to the final report tarball
  Copy snap list to the final report tarball
  Copy VM name (or none) to the final report tarball
  Copy current linux distribution to the final report tarball
  Copy network configuration to the final report tarball
Inspecting kubernetes cluster
  Inspect kubernetes cluster
Inspecting dqlite
  Inspect dqlite

Building the report tarball
  Report tarball is at /var/snap/microk8s/4567/inspection-report-20230220_120100.tar.gz
ubuntu@microk8s-vm:~$ microk8s status
microk8s is not running. Use microk8s inspect for a deeper inspection.

I would expect some sort of error somewhere. Either when joining the cluster, or when starting microk8s, or somewhere. It's also strange that status reports that it's not running, but inspect seems to think all the services are running.

[mlb5000]

/var/snap/microk8s/current/var/kubernetes/backend/cluster.yaml contains the microk8s-vm IP address on both the remote nodes and the microk8s-vm node itself.

[mlb5000]

Inspection Report: https://drive.google.com/file/d/1PIxdJHVfmkY01NJ8g1G1h4a1FHAucFGH/view?usp=share_link

[mlb5000]

Can I get any feedback on this?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.