canonical
HA-cluster addon forces MicroK8s to behave as a control-plane node
Summary
Even after a full OS reinstallation(24.04 LTS) and immediately trying to disable ha-cluster with --force, the ha-cluster addon on Pi 5 4GB is still enabled. The ha-cluster addon forces MicroK8s to behave as a control-plane node (running its own dqlite datastore, API server, etc.). I am trying to configure it as a worker node to later join it with my other Pi 5 8GB (control-plane).
What Should Happen Instead?
ha-cluster successfully disables and datastore master nodes goes away(worker node)
Reproduction Steps
After my 3rd attempts
- Download and install Ubuntu 24.04 LTS(64bit) server to SD card with Pi imager
- Configure network and initial boot on Pi
- Update, upgrade then reboot
- Install MicroK8s
sudo snap install microk8s --classic
- Add user to MicroK8s group
- Verify MicroK8s installation
microk8s status --wait-ready >> ... >> datastore master nodes: 127.0.0.1:19001 >> ... >> ha-cluster # (core) Configure high availability on the current node
- Disable ha-cluster
sudo microk8s disable ha-cluster --force
- Verify ha-cluster is disabled
sudo microk8s status | grep ha-cluster >> ha-cluster # (core) Configure high availability on the current node
Introspection Report
inspection-report-20250527_104122.tar.gz
Can you suggest a fix?
Are you interested in contributing with a fix?
no
Hey @jpbeniopa,
Microk8s already supports joining nodes as workers via the --worker flag of the join command. This resets the joining node, disables the datastore and any control-plane related services. See the clustering docs for more information. Thanks.
