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
Describe the feature you'd like to have.
Allow to specify nodeSelector to pods deployed for a (backup) jobs
What is the value to the end user? (why is it a priority?)
Improves the granularity on which nodes is volsync allowed to run.
How will we know we have a good solution? (acceptance criteria)
A helm chart allows either to specify nodeSelector for job pods or share the preexisting nodeSelector for the volsync operator.
Additional context
Since the current release does not have ARM builds, backing up jobs fail due to them being scheduld on ARM nodes. This would allow volsync to run in mixed clusters.
Describe the feature you'd like to have.
Allow to specify nodeSelector to pods deployed for a (backup) jobs
What is the value to the end user? (why is it a priority?)
Improves the granularity on which nodes is volsync allowed to run.
How will we know we have a good solution? (acceptance criteria)
A helm chart allows either to specify nodeSelector for job pods or share the preexisting nodeSelector for the volsync operator.
Additional context
Since the current release does not have ARM builds, backing up jobs fail due to them being scheduld on ARM nodes. This would allow volsync to run in mixed clusters.
#828
The text was updated successfully, but these errors were encountered: