Skip to content
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

Allow to specify nodeSelector to pod deployed by a (backup) jobs #1576

Closed
sambartik opened this issue Mar 4, 2025 · 2 comments
Closed

Allow to specify nodeSelector to pod deployed by a (backup) jobs #1576

sambartik opened this issue Mar 4, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@sambartik
Copy link

sambartik commented Mar 4, 2025

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

@sambartik sambartik added the enhancement New feature or request label Mar 4, 2025
@tesshuflower
Copy link
Contributor

This PR added the functionality of setting affinity for mover pods - would this give you what you need?

#1340

@sambartik
Copy link
Author

Indeed, it does. I was not of that property in a mover config. Thanks for the tip!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests

2 participants