You are looking at the documentation of a prior release. To read the documentation of the latest release, please visit here.

New to KubeDB? Please start here.

Reconfiguring ProxySQL

This guide will give an overview on how KubeDB Ops Manager reconfigures ProxySQL.

Before You Begin

How Reconfiguring ProxySQL Process Works

The following diagram shows how KubeDB Ops Manager reconfigures ProxySQL database components. Open the image in a new tab to see the enlarged version.

  Reconfiguring process of ProxySQL
Fig: Reconfiguring process of ProxySQL

The Reconfiguring ProxySQL 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 PetSets and related necessary stuff like secrets, services, etc.

  4. Then, in order to reconfigure the ProxySQL standalone or cluster the user creates a ProxySQLOpsRequest CR with desired information.

  5. KubeDB Enterprise operator watches the ProxySQLOpsRequest CR.

  6. Then the KubeDB Enterprise operator will replace the existing configuration with the new configuration provided or merge the new configuration with the existing configuration according to the ProxySQLOpsRequest CR.

In the next docs, we are going to show a step by step guide on reconfiguring ProxySQL database components using ProxySQLOpsRequest CRD.