Kinda relevant as the article won’t really help - what would you use for HA MySQL in a non-Kubernetes setting? Getting automated failovers, deployment of new nodes, and ~50k databases?
https://www.percona.com/blog/orchestrator-for-managing-mysql...
Please do some additional research into the state of maintenance of that piece of tech before jumping on it. But it certainly did a lot of powerful things for us back in the day. The automatic promotion of followers was key to our deployment.
Well kinda. Galera looks like it's an amazing solution, and it can be for careful operators who read the docs, learn the new procedures and ensure that they're running workloads that fit well. It can eliminate the usual HA / replication / failover stuff. But it has the ability to act like a foot-machinegun.
Outside kubernetes where you don't have an kubernetes operator that can run the database cluster, spin up nodes and pods, manage volumes etc it's difficult to imagine how you might automate that infrastructure in addition to managing the database cluster, without building a lot of it yourself.
Make sure you up ulimit and systemd LimitNOFILE in the MySQL service config. Read docs closely, preferably bring on someone who's spent some time making mistakes in this area to help out, test diligently before putting into production, including load tests.