-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Job / Pod specs of jobs should be configurable #7911
Comments
You can use the |
But we don't want to run the Velero deployment on the same nodes as the maintenance jobs. For example we use spot instances in some environments, which can be restartet every time by azure. They are ideal for short running jobs but we don't want to have some system critical services on them... Also stuff like the job history limit we can't configure in the deployment. |
Configuring the node selector for the maintenance job is a valid use case tracked by #7758. |
We have a lot of nodes so we're working with topologyspreadconstraints and node affinites to spread services evenly over our nodes. |
Please correct me if I'm wrong. So NodeAffinities is enough for this case. What's your opinion? |
True, for a job node affinity together with tolerations would be used. Currently we have 133 finished (most of them are repo-maintain-job) jobs in the velero namepsace. It might help if the jobs would be created out of cronjob resource. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands. |
This issue was closed because it has been stalled for 14 days with no activity. |
Describe the problem/challenge you have
When Velero runs maintenance or backup jobs the pod spec is not configurable. As we have a lod of nodes which make use of taints these workloads can't be scheduled there.
Describe the solution you'd like
We would need to adjust the tolerations and affinites for such jobs. Therefore the whole job / pod template should be configurable (we also woud like to be able to configure other stuff like securtiycontexts, job history and so on).
Anything else you would like to add:
Environment:
velero version
):velero client config get features
):kubectl version
):/etc/os-release
): ubuntuVote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: