High availability does not kick in
pmatulis opened this issue · 2 comments
pmatulis commented
My understanding is that HA gets configured automatically by virtue of at least three nodes being present. However, I do not see evidence of this.
I used the add-node
command to create a three-node cluster. This is what I have:
kubectl get nodes
NAME STATUS ROLES AGE VERSION
microk8s1 Ready <none> 100m v1.31.1
microk8s2 Ready <none> 90m v1.31.1
microk8s3 Ready <none> 88m v1.31.1
Yet HA is not kicking in:
microk8s status
microk8s is running
high-availability: no
datastore master nodes: 10.54.53.229:19001
datastore standby nodes: none
.
.
.
I'm using snap channel 1.31.1/stable
.
Where did I go wrong?
pmatulis commented
Closing for now. I believe that I need to ensure that the extra two nodes are not joined as "worker" nodes.
pmatulis commented
Confirmed. Sorry for the noise.