Horizontal Pod Autoscaloing (HPA) governs the spinning up and deletion of additional pods when the existing resources (CPU and Memory) of the microservice are exhausted. In Adeptia Connect, Autoscaling is by default disabled. You can enable HPA in Adeptia Connect by setting the required parameters in the global values.yaml file.
Follow the steps given below to configure HPA.
...
To enable HPA, you need to set the parameters as described below for each of the microservices individually.
The following screenshot illustrates the autoscaling parameters for webrunner microservice.
| Parameter | Descrition |
|---|---|
| enabled | Parameter to enable HPA by setting its value to true. |
| minReplicas | Minimum number of pods for a microservice. |
| maxReplicas | The maximum number of pods to which a microservice can scale up. |
| targetCPUUtilizationPercentage | The percentage value of CPU utilization beyond which the autoscaler spins up a new pod. |
| targetmemoryUtilizationPercentage | The percentage value of memory utilization beyond which the autoscaler spins up a new pod. |
Runtime HPA:
no of pf in queued state - shared/Autoscaling
Run time pod (RabbitMQ_Concurrency :10)
For shared queue - runtime
Autoscaliing: Threshold : 5
12 PF : 10 Running , 2 Queue
16PF : 10 running, 6: queue
For dedicated queue, we have option in UI.
...