HA-cluster addon forces MicroK8s to behave as a control-plane node

[jpbeniopa]

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

1. Download and install Ubuntu 24.04 LTS(64bit) server to SD card with Pi imager
2. Configure network and initial boot on Pi
3. Update, upgrade then reboot
4. Install MicroK8s

   sudo snap install microk8s --classic

5. Add user to MicroK8s group
6. 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

7. Disable ha-cluster

   sudo microk8s disable ha-cluster --force

8. 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