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.

Elasticsearch Storange Autoscaling

This guide will give an overview on how KubeDB Autoscaler operator autoscales the Elasticsearch storage using elasticsearchautoscaler crd.

Before You Begin

How Storage Autoscaling Works

The Auto Scaling process consists of the following steps:

  1. At first, a user creates a Elasticsearch Custom Resource (CR).

  2. KubeDB Provisioner operator watches the Elasticsearch CR.

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

  • Each StatefulSet creates a Persistent Volume according to the Volume Claim Template provided in the statefulset configuration.
  1. Then, in order to set up storage autoscaling of the various components of the Elasticsearch database the user creates a ElasticsearchAutoscaler CRO with desired configuration.

  2. KubeDB Autoscaler operator watches the ElasticsearchAutoscaler CRO.

  3. KubeDB Autoscaler operator continuously watches persistent volumes of the databases to check if it exceeds the specified usage threshold.

  • If the usage exceeds the specified usage threshold, then KubeDB Autoscaler operator creates a ElasticsearchOpsRequest to expand the storage of the database.
  1. KubeDB Ops-manager operator watches the ElasticsearchOpsRequest CRO.

  2. Then the KubeDB Ops-manager operator will expand the storage of the database component as specified on the ElasticsearchOpsRequest CRO.

In the next docs, we are going to show a step-by-step guide on Autoscaling storage of various Elasticsearch database components using ElasticsearchAutoscaler CRD.