chilly-caravan-31853
08/26/2022, 10:22 AM--cluster-init
argument, then added two more Nodes B and C with the --server A
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 (k3s kubectl get nodes
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.hundreds-evening-84071
08/26/2022, 1:18 PMkubectl get nodes
report api errors?wonderful-baker-81666
08/26/2022, 2:24 PMchilly-caravan-31853
08/29/2022, 3:37 AM2 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-84071
08/29/2022, 1:35 PMchilly-caravan-31853
08/30/2022, 4:42 AMhundreds-evening-84071
08/30/2022, 5:09 PMchilly-caravan-31853
08/31/2022, 7:47 AMapiserver not ready
error from the remaining node's 6443 port. Switching 1 node on (to make the total of 2) fixes the cluster.