High Availability
To enable autoscaling for Temporal services, you need to update the values/temporal-values.yaml
configuration. This step-by-step guide shows how to configure autoscaling parameters for various Temporal components, including frontend
, history
, matching
, and worker
.
Update the Autoscaling Configuration in
temporal-values.yaml
for Each Temporal ServiceFrontend Configuration:
Modify the
replicaCount
,autoscaling
, andresources
sections as follows:Setting
autoscaling.enabled
totrue
activates autoscaling for the frontend service. AdjustminReplicas
andmaxReplicas
according to your expected load and resource availability.
History Configuration:
Update the
history
service settings:This configuration ensures the
history
service can scale within the specified limits based on CPU and memory usage.
Matching Configuration:
Configure the
matching
service:Autoscaling is controlled by the resource thresholds specified. You can adjust these thresholds based on the demand expected on the
matching
service.
Worker Configuration:
Configure the
worker
service:Autoscaling is controlled by the resource thresholds specified. You can adjust these thresholds based on the demand expected on the
worker
service.
Update the Autoscaling Configuration in
nected-values.yaml
for Each Nected Service like vidhaan-executer and vidhaan-router.Vidhaan Executer
Configure the
vidhaan-executer
service:
Vidhaan Router
Configure the
vidhaan-router
service:
Autoscaling is controlled by the resource thresholds specified. You can adjust these thresholds based on the demand expected on the matching
service.
Last updated