-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scale Jobs-runner resources separately from main_backend #186
base: main
Are you sure you want to change the base?
Conversation
charts/retool/values.yaml
Outdated
@@ -231,7 +231,7 @@ extraVolumeMounts: [] | |||
|
|||
extraVolumes: [] | |||
|
|||
# These resource specifications apply to the main backend and workflows backend pods. | |||
# These resource specifications will apply to the main backend, jobs-runner, db-connector, and workflows backend pods(unless if container specific resources are set) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit, reword:
These resource specifications will apply to the main backend, jobs-runner, dbconnector, and workflows-backend pods unless container specific resources are set.
charts/retool/values.yaml
Outdated
@@ -299,6 +299,15 @@ jobRunner: | |||
# will already launch a job runner pod | |||
# enabled: true | |||
|
|||
# These resource apply only to the jobs-runner pod. Set the resources to scale jobs-runner pod separately from main-backend pods. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit reword:
If necessary, specify the resources to provision the jobRunner pod separately from the main backend pods.
Added option to set resource.request/limit for jobs-runner container. Separating it from same resources used in for main backend