New to KubeDB? Please start here.

Vertical Scaling MySQL

This guide will give you an overview of how KubeDB Ops Manager updates the resources(for example Memory and RAM etc.) of the MySQL database server.

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • MySQL
  • MySQLOpsRequest

How Vertical Scaling Process Works

The following diagram shows how the KubeDB Ops Manager used to update the resources of the MySQL database server. Open the image in a new tab to see the enlarged version.

The vertical scaling process consists of the following steps:

1. At first, a user creates a MySQL cr.

2. KubeDB community operator watches for the MySQL cr.

3. When it finds one, it creates a PetSet and related necessary stuff like secret, service, etc.

4. Then, in order to update the resources(for example CPU, Memory etc.) of the MySQL database the user creates a MySQLOpsRequest cr.

5. KubeDB Ops Manager watches for MySQLOpsRequest.

6. 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.

7. Then the KubeDB Ops Manager will update resources of the PetSet replicas to reach the desired state.

8. After successful updating of the resources of the PetSet’s replica, the KubeDB Ops Manager updates the MySQL object resources to reflect the updated state.

9. After successful updating of the MySQL resources, the KubeDB Ops Manager resumes the MySQL object so that the KubeDB community operator resumes its usual operations.

Vertical Scaling Modes

KubeDB actuates vertical scaling in one of two modes, selected through the spec.verticalScaling.mode field of the MySQLOpsRequest:

• Restart (default): The operator patches the PetSet with the new resources and restarts the Pods (one at a time, honoring the database’s failover rules) so they come back with the updated CPU and Memory. This works on every Kubernetes cluster.
• InPlace: The operator resizes the running containers in place using the Kubernetes in-place Pod resize (pods/resize subresource) — no Pod restart, so scaling happens without downtime or failover. If a Node cannot accommodate the new resources (the resize is reported Infeasible), the operator automatically falls back to the Restart behavior for that Pod.

If spec.verticalScaling.mode is omitted, it defaults to Restart.

Note: InPlace mode relies on the Kubernetes InPlacePodVerticalScaling feature gate, which is enabled by default from Kubernetes v1.33. On older clusters, or when the feature gate is disabled, use Restart mode.

In the next doc, we are going to show a step by step guide on updating resources of MySQL database using vertical scaling operation.