New to KubeDB? Please start here.

ProxySQL Vertical Scaling

This guide will give an overview on how KubeDB Ops Manager vertically scales up ProxySQL.

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • ProxySQL
  • ProxySQLOpsRequest

How Vertical Scaling Process Works

The following diagram shows how KubeDB Ops Manager scales up or down ProxySQL instance resources. 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 ProxySQL Custom Resource (CR).

2. KubeDB Community operator watches the ProxySQL CR.

3. When the operator finds a ProxySQL CR, it creates required number of StatefulSets and related necessary stuff like secrets, services, etc.

4. Then, in order to update the resources(for example CPU, Memory etc.) of the ProxySQL the user creates a ProxySQLOpsRequest CR with desired information.

5. KubeDB Enterprise operator watches the ProxySQLOpsRequest CR.

6. When it finds a ProxySQLOpsRequest CR, it halts the ProxySQL object which is referred from the ProxySQLOpsRequest. So, the KubeDB Community operator doesn’t perform any operations on the ProxySQL object during the vertical scaling process.

7. Then the KubeDB Enterprise operator will update resources of the StatefulSet Pods to reach desired state.

8. After the successful update of the resources of the StatefulSet’s replica, the KubeDB Enterprise operator updates the ProxySQL object to reflect the updated state.

9. After the successful update of the ProxySQL resources, the KubeDB Enterprise operator resumes the ProxySQL object so that the KubeDB Community operator resumes its usual operations.

In the next docs, we are going to show a step by step guide on updating resources of ProxySQL using ProxySQLOpsRequest CRD.