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.
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
- You should be familiar with the following
KubeDB
concepts:
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](/docs/v2023.11.2/guides/postgres/scaling/vertical-scaling/overview/images/pg-vertical-scaling.png)
The vertical scaling process consists of the following steps:
At first, a user creates a
Postgres
cr.KubeDB
community operator watches for thePostgres
cr.When it finds one, it creates a
StatefulSet
and related necessary stuff like secret, service, etc.Then, in order to update the resources(for example
CPU
,Memory
etc.) of thePostgres
database the user creates aPostgresOpsRequest
cr.KubeDB
enterprise operator watches forPostgresOpsRequest
.When it finds one, it halts the
Postgres
object so that theKubeDB
Provisioner operator doesn’t perform any operation on thePostgres
during the scaling process.Then the
KubeDB
Ops Manager operator will update resources of the StatefulSet replicas to reach the desired state.After successful updating of the resources of the StatefulSet’s replica, the
KubeDB
enterprise operator updates thePostgres
object resources to reflect the updated state.After successful updating of the
Postgres
resources, theKubeDB
Ops Manager resumes thePostgres
object so that theKubeDB
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.