Page Comparison

...

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 shared ashared or dedicated queue. The sections given below describe how the runtime HPA behaves 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:

...

If you want to configure the HPA after deployment of the application, follow the steps given below.

1. Go to /shared folder in the PVC.
2. Open AUTOSCALING file in edit mode.

3. Provide Update the values file as shown in the example below.

   Code Block
   language css theme Midnight
   2|3|7|My_Namespace|shared_queue|deployment_1

   Where,

   2 - Minimum number of pods for runtime microservice.

   3 - The maximum number of pods the runtime microservice can scale up to.

   7 - The number of Process Flows in the shared queue beyond which the autoscaler spins up a new runtime pod.

   My_Namespace - Namespace

   shared_queue - Name of the shared queue

   deployment_1 - Name of the deployment

4. Save the file.
5. Restart the runtime microservice.

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 following the steps given on the page "Creating a queue".