We use cookies and other similar technology to collect data to improve your experience on our site, as described in our Privacy Policy.
Run Production-Grade Databases on Kubernetes
Backup and Recovery Solution for Kubernetes
Run Production-Grade Vault on Kubernetes
Secure HAProxy Ingress Controller for Kubernetes
Kubernetes Configuration Syncer
Kubernetes Authentication WebHook Server
KubeDB simplifies Provision, Upgrade, Scaling, Volume Expansion, Monitor, Backup, Restore for various Databases in Kubernetes on any Public & Private Cloud
A complete Kubernetes native disaster recovery solution for backup and restore your volumes and databases in Kubernetes on any public and private clouds.
KubeVault is a Git-Ops ready, production-grade solution for deploying and configuring Hashicorp's Vault on Kubernetes.
Secure HAProxy Ingress Controller for Kubernetes
Kubernetes Configuration Syncer
Kubernetes Authentication WebHook Server
New to KubeDB? Please start here.
This guide will give you an overview of how KubeDB
Ops Manager scales up/down the number of members of a MySQL
group replication.
KubeDB
concepts:
The following diagram shows how KubeDB
Ops Manager used to scale up the number of members of a MySQL
group replication. Open the image in a new tab to see the enlarged version.
The horizontal scaling process consists of the following steps:
At first, a user creates a MySQL
cr.
KubeDB
community operator watches for the MySQL
cr.
When it finds one, it creates a StatefulSet
and related necessary stuff like secret, service, etc.
Then, in order to scale the cluster, the user creates a MySQLOpsRequest
cr with the desired number of members after scaling.
KubeDB
Ops Manager watches for MySQLOpsRequest
.
When it finds one, it halts the MySQL
object so that the KubeDB
community operator doesn’t perform any operation on the MySQL
during the scaling process.
Then the KubeDB
Ops Manager will scale the StatefulSet replicas to reach the expected number of members for the group replication.
After successful scaling of the StatefulSet’s replica, the KubeDB
Ops Manager updates the spec.replicas
field of MySQL
object to reflect the updated cluster state.
After successful scaling of the MySQL
replicas, the KubeDB
Ops Manager resumes the MySQL
object so that the KubeDB
community operator can resume its usual operations.
In the next doc, we are going to show a step by step guide on scaling of a MySQL group replication using Horizontal Scaling.