temporalio / helm-charts

Temporal Helm charts
MIT License
294 stars 321 forks source link

[Feature Request] Ability to set ReplicaCount for Frontend, History, Matching and Worker pods #386

Closed vishwa-trulioo closed 10 months ago

vishwa-trulioo commented 1 year ago

Is your feature request related to a problem? Please describe.

According to the Temporal Server documentation, it is recommended to have 5 Frontend, 15 History, 17 Matching, and 3 Worker Services per cluster in real-life production deployments. But as of now, it is not possible. The helm chart provides a single variable server.replicaCount which commonly set the value for frontend, history, matching and worker services. I would like the ability to set replica count individually if a user prefers to do so when setting up production environments. Perhaps it would be good to offer the same for other supporting services like web, admintools, kube-state-metrics as well.

Describe the solution you'd like

Ability to set individual replica counts for cluster services, in the form of,

helm install -f values/values.mysql.yaml temporaltest \
  --set frontend.replicaCount=5 \
  --set history.replicaCount=15 \
  --set matching.replicaCount=17 \
  --set worker.replicaCount=3 \
  --set web.replicaCount=2 \
  --set admintools.replicaCount=2 . --timeout 900s

Additional context

imporoutco586 commented 11 months ago

Maybe you can set replicaCount in every service, than you can do that. like this:

frontend:
    replicaCount: 5
 matching:
    replicaCount: 3
vishwa-trulioo commented 10 months ago

Thanks for the help. We can close this issue.