New to KubeDB? Please start here.

This is an Enterprise-only feature. Please install KubeDB Ops Manager to try this feature.

Vertical Scaling Postgres

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

Before You Begin

How Vertical Scaling Process Works

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

Vertical scaling Flow
Fig: Vertical scaling process of Postgres

The vertical scaling process consists of the following steps:

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

  2. KubeDB community operator watches for the Postgres cr.

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

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

  5. KubeDB enterprise operator watches for PostgresOpsRequest.

  6. When it finds one, it halts the Postgres object so that the KubeDB Provisioner operator doesn’t perform any operation on the Postgres during the scaling process.

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

  8. After successful updating of the resources of the StatefulSet’s replica, the KubeDB enterprise operator updates the Postgres object resources to reflect the updated state.

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

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