This message was deleted.
# k3s
a
This message was deleted.
c
its pretty chatty, yeah. The throughput will be proportional to the load on the apiserver.
s
For a HA setup you need 3 or 5 control plane nodes.
c
not with external sql you don’t
f
@creamy-pencil-82913 You mean this is normal,right? Meanwhile, another master has little throughout, no load-balance. @sparse-fireman-14239 In my opinion, the apiserver is stateless, several apiservers just for load-balance, not for election,right?Additionally,two masters are written in docs(Two or more server nodes) :)
r
Well...technically you're HA as long as the external database stays up. Is your MySQL instance running on >1 node?
c
Correct, apiservers are stateless but the controllers are leader-elected and talk to the local apiserver. So you will effectively always have one node that's active and others standby
The odd number of nodes restriction is just for etcd and doesn't apply if you're using an external datastore
f
@rough-farmer-49135 Yes, there is only one MySQL instance running on one node.
r
That means that if you want to test how things work with an HA Kubernetes cluster, you're good. However if you're trying to protect yourself from a single point of failure, you've just moved it back from the control plane to the MySQL instance.