...
| 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 HPA configuration for the runtime microservice differs from that of the rest of the microservices. An additional runtime pod spins up or gets deleted based on the number of Process Flows you have in the queued state. As the number of Process Flows in the queue gets beyond the threshold value, a new runtime pod is created.
The configuration steps for HPA depend upon whether the Process Flows are running on ashared or dedicated queue. The sections given below describe how the runtime HPA is configured in the following scenarios.
When the Process Flows to run on the shared queue
If you are configuring the HPA before deployment of the application, set the parameters in the global values.yaml file as instructed below:
...
| Info |
|---|
| Changes are reflected within 30 secs. |
When the Process Flows to run on a dedicated queue
If your Process flows are running on a dedicated queue, you can configure the HPA by followng the steps given on the page "Creating a queue".
...