I’ve installed Microk8s on 64bit Raspberry Pi OS (formally Raspbian) through snap, on three RPis - master node and two workers nodes (which joined the cluster). All works fine but for one detail:
I hoped not to have master node be part of the cluster and when I remove itself from it (remove node) all still works well as I can tell (deployed test container, configured all with metallb and such) but I’ve got 100MB of logs each day with something like:
microk8s.daemon-kubelet: E0728 17:03:39.371723 11580 kubelet.go:2268] node "my-master-host-name" not found
BTW - all seem like clean install (sorted all issues and
microk8s inspect returns clean bill of health) and I did it several times just to be sure I know what I am doing and if I keep master node to be part of the cluster all is fine (I did cordoned it at the end).
Question is: is that some kind of bug or misconfiguration I am hitting or master node shouldn’t ever be removed from the cluster itself?
Just to say it again - I haven’t done anything extra from what snap package did in terms of installation and/or configuration - just installed it on three RPis, added two to the master and removed master from the cluster when logs started. And repeated steps on clean install again it just for confirmation.
Kubernetes version: snap returns microk8s v1.18.6 1558 latest/stable canonical✓ classic
Cloud being used: bare-metal on RPis
Installation method: snapd
Host OS: Raspberry Pi OS (debian derived 64bit arm linux)
CNI and version:
CRI and version: