The repo maintenance job should support node selector #7758
Comments
|
IMO, reuse the ConfigMap mentioned in this design to generate the maintenance Job is enough. I am checking with the issue reporter whether that is acceptable. |
|
First, if we create a configuration for the repository maintenance Job, related information should be all put there, not only the node selector, for example, the Job's resource configuration should be considered too. Second, is it reasonable to make the node selection configuration per BackupRepository? It's a bit overkill for the node selection, but the resource configuration could differ for different BackupRepositories. |
3 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The repository maintenance jobs may be running for some time and consume substantial resource.
Like datamover, we should support node-selector for these jobs. Ideally we should reuse the data structures of node selectors for data mover and provide a similar user experience in terms of setting the node selectors.
The text was updated successfully, but these errors were encountered: