Support for nodeSelector, tolerations, affinity, and resources (limits/requests) in migration jobs

[BrianSiimAndersenEG]

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 for nodeSelector, tolerations, affinity, and resources 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

[github-actions]

WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible.
The roadmap is driven by our customers and we have to prioritize issues that are important to them.
You can influence the priority by becoming a customer. Please contact us here.

[Aenimus]

Hi @BrianSiimAndersenEG

Please could you elaborate on your use case?

Thanks!

[BrianSiimAndersenEG]

Hi @Aenimus - sorry for the long response time.

In the cluster we have multiple namespaces and the default node is very restricted. In the values.yaml for all the components, your Helm chart makes it possible to specify tolerations, affinity, and resources. We use that to make the components run in given nodes, and our cluster is also set up, so that we have to specify the resources. This is working perfectly with all the components.

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.