Engineering teams transitioning to a Kubernetes-native infrastructure face significant challenges in reliably running databases within clusters. This includes ensuring high availability, backups, and disaster recovery for production systems like MySQL and MariaDB. Team strategies have included migrating PostgreSQL using the Crunchy Postgres Operator, which has been successful in providing the needed reliability. However, choosing suitable operators for MariaDB and MySQL required setting precise production-grade criteria to meet their operational needs effectively, indicating the importance of thorough planning in the migration process.
One team shared their strategy: migrating databases like PostgreSQL, MariaDB, MySQL, and H2 off VMs into Kubernetes, prioritizing high availability and effective operators.
The decision for suitable database operators for MariaDB and MySQL was not straightforward, leading the team to establish clear production-grade requirements.
Collection
[
|
...
]