You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
For production deployments the JobSet controller manager resource requests and limits should be configured to align with the specific infrastructure it will be deployed on.
Why is this needed:
We need to lower the default resource requests to address a widespread usability issue users encounter when trying out JobSet for the first time and getting confused when they can't create JobSets after installing the CRD (controller manager pod stays pending due to not fitting on default cloud VM nodes). However, for production deployments users should not rely on the defaults and should patch them to be optimized for their prod deployment infrastructure.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
For production deployments the JobSet controller manager resource requests and limits should be configured to align with the specific infrastructure it will be deployed on.
We should add guidance in the installation docs showing the user how to patch the deployment resource requests/limits for prod deployments: https://kubernetes.io/docs/tasks/manage-kubernetes-objects/update-api-object-kubectl-patch/#use-a-strategic-merge-patch-to-update-a-deployment
Why is this needed:
We need to lower the default resource requests to address a widespread usability issue users encounter when trying out JobSet for the first time and getting confused when they can't create JobSets after installing the CRD (controller manager pod stays pending due to not fitting on default cloud VM nodes). However, for production deployments users should not rely on the defaults and should patch them to be optimized for their prod deployment infrastructure.
The text was updated successfully, but these errors were encountered: