Let’s be honest: migrating a relational database to Kubernetes sounds fantastic in a whiteboard meeting, but the reality of day-two operations is a completely different story.
When moving MySQL to Kubernetes, the ultimate goal is simple: identify a safe, performant set of configuration values for your database pods. But where do you start? Usually, you look at your overall node resources say, a machine with 16 CPUs and 64GB of RAM.
In the old bare-metal days, you'd apply the standard rules of thumb:
-
Set
innodb_buffer_pool_sizeto 60-80% of total RAM to maximize caching. -
Allocate 1
innodb_buffer_pool_instancesper 1GB of buffer pool. -
Match
innodb_io_capacityto your drive speeds.
If you try applying these legacy rules in Kubernetes, your pod won't survive. …
[Read more]