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.
This guide will give an overview on how KubeDB Autoscaler operator autoscales the Elasticsearch storage using elasticsearchautoscaler
crd.
KubeDB
concepts:The Auto Scaling process consists of the following steps:
At first, a user creates a Elasticsearch
Custom Resource (CR).
KubeDB
Community operator watches the Elasticsearch
CR.
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. This Persistent Volume will be expanded by the KubeDB
Enterprise operator.
Then, to set up storage autoscaling of the various nodes (ie. master, data, ingest, etc.) of the Elasticsearch
cluster the user creates a ElasticsearchAutoscaler
CRO with the desired configuration.
KubeDB
Autoscaler operator watches the ElasticsearchAutoscaler
CRO.
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.
KubeDB
Enterprise operator watches the ElasticsearchOpsRequest
CRO.
Then the KubeDB
Enterprise 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.