This message was deleted.
# kubernetes
a
This message was deleted.
b
You can choose a different backing mechanism. K3s permits for a mysql connection instead of etcd, but if the responses aren't under the expected time you're gonna have the same problem.
Mysql can be external to the cluster
I think an engineer told me as a general rule the responses should be < 2ms and after 15 ms you start to see problems (we were on spinners too and ours were like 200 ms)
b
Thanks for response. I'm going to tune up etcd and see if it helps. If not then I'm going to move etcd to a separate machines - maybe it will help. Moving it to mysql or postgresql doesn't seem a good idea - but we will see - maybe there won't be a choice 😞
b