New to KubeDB? Please start here.
Elasticsearch Horizontal Scaling
This guide will give an overview on how KubeDB Ops-manager operator scales up or down Elasticsearch cluster replicas of various components.
Before You Begin
- You should be familiar with the following
KubeDBconcepts:
How Horizontal Scaling Process Works
The following diagram shows how KubeDB Ops-manager operator scales up or down Elasticsearch database components. Open the image in a new tab to see the enlarged version.

The Horizontal scaling process consists of the following steps:
At first, a user creates a
ElasticsearchCustom Resource (CR).KubeDBProvisioner operator watches theElasticsearchCR.When the operator finds a
ElasticsearchCR, it creates required number ofPetSetsand related necessary stuff like secrets, services, etc.Then, in order to scale the various components of the
Elasticsearchcluster, the user creates aElasticsearchOpsRequestCR with desired information.KubeDBOps-manager operator watches theElasticsearchOpsRequestCR.When it finds a
ElasticsearchOpsRequestCR, it halts theElasticsearchobject which is referred from theElasticsearchOpsRequest. So, theKubeDBProvisioner operator doesn’t perform any operations on theElasticsearchobject during the horizontal scaling process.Then the
KubeDBOps-manager operator will scale the related PetSet Pods to reach the expected number of replicas defined in theElasticsearchOpsRequestCR.After the successfully scaling the replicas of the related PetSet Pods, the
KubeDBOps-manager operator updates the number of replicas in theElasticsearchobject to reflect the updated state.After the successful scaling of the
Elasticsearchreplicas, theKubeDBOps-manager operator resumes theElasticsearchobject so that theKubeDBProvisioner operator resumes its usual operations.
In the next docs, we are going to show a step by step guide on horizontal scaling of Elasticsearch cluster using ElasticsearchOpsRequest CRD.































