diff --git a/charts/retool/templates/deployment_workflows.yaml b/charts/retool/templates/deployment_workflows.yaml index a1d5e75d..1f04d8a8 100644 --- a/charts/retool/templates/deployment_workflows.yaml +++ b/charts/retool/templates/deployment_workflows.yaml @@ -11,7 +11,7 @@ metadata: {{ toYaml .Values.deployment.annotations | indent 4 }} {{- end }} spec: - replicas: 1 + replicas: {{ ((.Values.workflows.backend).replicaCount) | default 1 }} selector: matchLabels: retoolService: {{ template "retool.fullname" . }}-workflow-backend diff --git a/charts/retool/templates/deployment_workflows_worker.yaml b/charts/retool/templates/deployment_workflows_worker.yaml index 211a2013..4353178c 100644 --- a/charts/retool/templates/deployment_workflows_worker.yaml +++ b/charts/retool/templates/deployment_workflows_worker.yaml @@ -11,7 +11,7 @@ metadata: {{ toYaml .Values.deployment.annotations | indent 4 }} {{- end }} spec: - replicas: {{ .Values.workflows.replicaCount }} + replicas: {{ (.Values.workflows.worker).replicaCount | default (.Values.workflows.replicaCount | default 1) }} selector: matchLabels: retoolService: {{ template "retool.fullname" . }}-workflow-worker diff --git a/charts/retool/values.yaml b/charts/retool/values.yaml index 880b691c..4a6bc8b8 100644 --- a/charts/retool/values.yaml +++ b/charts/retool/values.yaml @@ -301,29 +301,35 @@ workflows: # explicitly set other fields as needed # enabled: true - # A replicaCount of 1 will launch 6 pods -- 1 workflow backend, 1 workflow worker, and 4 pods that make up the executor temporal cluster - # Scaling this number will increase the number of workflow workers, e.g. a replicaCount of 4 - # will launch 9 pods -- 1 workflow backend, 4 workflow workers, and 4 for temporal cluster # ADVANCED: The temporal cluster can be scaled separately in the subchart (charts/retool-temporal-services-helm/values.yaml) # If your needs require scaling temporal, reach out to us for guidance -- it is likely the bottleneck is DB or worker replicaCount - replicaCount: 1 + worker: + # A replicaCount of 1 will launch 6 pods -- 1 workflow backend, 1 workflow worker, and 4 pods that make up the executor temporal cluster + # Scaling this number will increase the number of workflow workers, e.g. a replicaCount of 4 + # will launch 9 pods -- 1 workflow backend, 4 workflow workers, and 4 for temporal cluster + replicaCount: 1 + + backend: + # A replicaCount of 1 will launch 6 pods -- 1 workflow backend, 1 workflow worker, and 4 pods that make up the executor temporal cluster + # Scaling this number will increase the number of workflow backends, e.g. a replicaCount of 4 + # will launch 9 pods -- 4 workflow backend, 1 workflow workers, and 4 for temporal cluster + replicaCount: 1 # Timeout for queries, in ms. This will set the timeout for workflows-related pods only # If this value is not set but config.dbConnectorTimeout is, we will set workflows pod timeouts # to .Values.config.dbConnectorTimeout # dbConnectorTimeout: 120000 - # Annotations for workflows worker pods + # Annotations for workflows worker and workflow backend pods annotations: {} - # Labels for workflows worker pods + # Labels for workflows worker and workflow backend pods labels: {} # IMPORTANT: Incompatible with retool-temporal-services-helm subchart # This allows configuring a Retool Workflows deployment that uses your own Temporal cluster # instead of deploying a new one. Set enabled to true and add the config variables. - # NOTE: Temporal Frontend with required TLS or mTLS not currently supported temporal: # set enabled to true if using a pre-existing temporal cluster enabled: false diff --git a/values.yaml b/values.yaml index 880b691c..4a6bc8b8 100644 --- a/values.yaml +++ b/values.yaml @@ -301,29 +301,35 @@ workflows: # explicitly set other fields as needed # enabled: true - # A replicaCount of 1 will launch 6 pods -- 1 workflow backend, 1 workflow worker, and 4 pods that make up the executor temporal cluster - # Scaling this number will increase the number of workflow workers, e.g. a replicaCount of 4 - # will launch 9 pods -- 1 workflow backend, 4 workflow workers, and 4 for temporal cluster # ADVANCED: The temporal cluster can be scaled separately in the subchart (charts/retool-temporal-services-helm/values.yaml) # If your needs require scaling temporal, reach out to us for guidance -- it is likely the bottleneck is DB or worker replicaCount - replicaCount: 1 + worker: + # A replicaCount of 1 will launch 6 pods -- 1 workflow backend, 1 workflow worker, and 4 pods that make up the executor temporal cluster + # Scaling this number will increase the number of workflow workers, e.g. a replicaCount of 4 + # will launch 9 pods -- 1 workflow backend, 4 workflow workers, and 4 for temporal cluster + replicaCount: 1 + + backend: + # A replicaCount of 1 will launch 6 pods -- 1 workflow backend, 1 workflow worker, and 4 pods that make up the executor temporal cluster + # Scaling this number will increase the number of workflow backends, e.g. a replicaCount of 4 + # will launch 9 pods -- 4 workflow backend, 1 workflow workers, and 4 for temporal cluster + replicaCount: 1 # Timeout for queries, in ms. This will set the timeout for workflows-related pods only # If this value is not set but config.dbConnectorTimeout is, we will set workflows pod timeouts # to .Values.config.dbConnectorTimeout # dbConnectorTimeout: 120000 - # Annotations for workflows worker pods + # Annotations for workflows worker and workflow backend pods annotations: {} - # Labels for workflows worker pods + # Labels for workflows worker and workflow backend pods labels: {} # IMPORTANT: Incompatible with retool-temporal-services-helm subchart # This allows configuring a Retool Workflows deployment that uses your own Temporal cluster # instead of deploying a new one. Set enabled to true and add the config variables. - # NOTE: Temporal Frontend with required TLS or mTLS not currently supported temporal: # set enabled to true if using a pre-existing temporal cluster enabled: false