Horizontal Pod Autoscaling (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.
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 | Description |
|---|---|
| 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 a microservice can scale up to. |
| targetCPUUtilizationPercentage | The percentage value of CPU utilization at which the autoscaler spins up a new pod. |
| targetmemoryUtilizationPercentage | The percentage value of memory utilization at which the autoscaler spins up a new pod. |
Configuring HPA for runtime microservice
The parameters for configuring the runtime microservice for autoscaling slightly differ from those for the rest of the microservices.
The following screenshot illustrates the autoscaling parameters for runtime microservice.
