New to KubeDB? Please start here.
IgniteAutoscaler
What is IgniteAutoscaler
IgniteAutoscaler is a Kubernetes Custom Resource Definitions (CRD). It provides a declarative configuration for autoscaling Ignite compute resources and storage of database components in a Kubernetes native way.
IgniteAutoscaler CRD Specifications
Like any official Kubernetes resource, a IgniteAutoscaler has TypeMeta, ObjectMeta, Spec and Status sections.
Here, some sample IgniteAutoscaler CROs for autoscaling different components of database is given below:
Sample IgniteAutoscaler for ignite cluster:
apiVersion: autoscaling.kubedb.com/v1alpha1
kind: IgniteAutoscaler
metadata:
name: ignite-autoscale-ops
namespace: demo
spec:
databaseRef:
name: ignite-autoscale
compute:
ignite:
trigger: "On"
podLifeTimeThreshold: 5m
resourceDiffPercentage: 20
minAllowed:
cpu: 600m
memory: 1.2Gi
maxAllowed:
cpu: 1
memory: 2Gi
controlledResources: ["cpu", "memory"]
containerControlledValues: "RequestsAndLimits"
Here, we are going to describe the various sections of a IgniteAutoscaler crd.
A IgniteAutoscaler object has the following fields in the spec section.
spec.databaseRef
spec.databaseRef is a required field that point to the Ignite object for which the autoscaling will be performed. This field consists of the following sub-field:
- spec.databaseRef.name : specifies the name of the Ignite object.
spec.opsRequestOptions
These are the options to pass in the internally created opsRequest CRO. opsRequestOptions has two fields.
spec.compute
spec.compute specifies the autoscaling configuration for the compute resources i.e. cpu and memory of the database components. This field consists of the following sub-field:
spec.compute.igniteindicates the desired compute autoscaling configuration for Ignite database.
spec.compute.ignite has the following sub-fields:
triggerindicates if compute autoscaling is enabled for this component of the database. If “On” then compute autoscaling is enabled. If “Off” then compute autoscaling is disabled.minAllowedspecifies the minimal amount of resources that will be recommended, default is no minimum.maxAllowedspecifies the maximum amount of resources that will be recommended, default is no maximum.controlledResourcesspecifies which type of compute resources (cpu and memory) are allowed for autoscaling. Allowed values are “cpu” and “memory”.containerControlledValuesspecifies which resource values should be controlled. Allowed values are “RequestsAndLimits” and “RequestsOnly”.resourceDiffPercentagespecifies the minimum resource difference between recommended value and the current value in percentage. If the difference percentage is greater than this value than autoscaling will be triggered.podLifeTimeThresholdspecifies the minimum pod lifetime of at least one of the pods before triggering autoscaling.
There are two more fields, those are only specifiable for the percona variant inMemory databases.
inMemoryStorage.UsageThresholdPercentageIf db uses more than usageThresholdPercentage of the total memory, memoryStorage should be increased.inMemoryStorage.ScalingFactorPercentageIf db uses more than usageThresholdPercentage of the total memory, memoryStorage should be increased by this given scaling percentage.
spec.storage
spec.storage specifies the autoscaling configuration for the storage resources of the database components. This field consists of the following sub-field:
spec.storage.igniteindicates the desired storage autoscaling configuration for Ignite cluster.
All of them has the following sub-fields:
triggerindicates if storage autoscaling is enabled for this component of the database. If “On” then storage autoscaling is enabled. If “Off” then storage autoscaling is disabled.usageThresholdindicates usage percentage threshold, if the current storage usage exceeds then storage autoscaling will be triggered.scalingThresholdindicates the percentage of the current storage that will be scaled.expansionModeindicates the volume expansion mode.































