chilly-caravan-3185308/26/2022, 10:22 AM
argument, then added two more Nodes B and C with the
argument. All seemed fine, but after I shut down all the three nodes and then start B and C only, the cluster is not operational (
on Node B gives the "apiserver not ready" error). What am I missing? Is the first A node still special and a single point of failure? It is also strange that I cannot locate an etcd pod on any of the nodes when they are running normally.
k3s kubectl get nodes
hundreds-evening-8407108/26/2022, 1:18 PM
report api errors?
kubectl get nodes
wonderful-baker-8166608/26/2022, 2:24 PM
chilly-caravan-3185308/29/2022, 3:37 AM
2 of the 3 nodes need to remain online for HA.That's interesting. Is it documented? I had experimented with a HA setup of 2 nodes with a PostgreSQL datastore, and it survived the loss of 1 node.
what happens in your setup if you only shutdown node A?The cluster remains operational.
hundreds-evening-8407108/29/2022, 1:35 PM
chilly-caravan-3185308/30/2022, 4:42 AM
hundreds-evening-8407108/30/2022, 5:09 PM
chilly-caravan-3185308/31/2022, 7:47 AM
error from the remaining node's 6443 port. Switching 1 node on (to make the total of 2) fixes the cluster.
apiserver not ready