-
Notifications
You must be signed in to change notification settings - Fork 96
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
Support for nodeSelector, tolerations, affinity, and resources (limits/requests) in migration jobs #692
Comments
WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible. |
Please could you elaborate on your use case? Thanks! |
Hi @Aenimus - sorry for the long response time. In the cluster we have multiple namespaces and the default node is very restricted. In the The "problem" is the migrations, that are running. As a workaround our cluster configuration has been changes, so that it's less restrictive, but we would very much like the opportunity to specify the mentioned properties for the migrations, in order for them to run in a specific node - which we handle through tolerations and affinity. |
Component(s)
helm
Is your feature request related to a problem? Please describe.
In the Helm charts for all the components for the Cosmo platform it is possible to override tolerations, affinity, and resources through
values.yaml
. This is not possible for the charts for the migration jobs. We're installing in a cluster which requires us to specify resource limits, and need to run in a node other that the default node.Describe the solution you'd like
We would like to be able to specify properties in the
values.yaml
fornodeSelector
,tolerations
,affinity
, andresources
and use those values within the charts for the migration jobs, so that we are able to run the migrations in specific nodes - like it is possible with the other charts.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: