Skip to content

Set affinity and tolerations to logical backup cronjob #1288

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.

Sign up for GitHub

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

Jump to bottom
Open
ondrejmichalcik opened this issue Jan 5, 2021 · 3 comments
Open

Set affinity and tolerations to logical backup cronjob #1288

ondrejmichalcik opened this issue Jan 5, 2021 · 3 comments

Comments

@ondrejmichalcik
Copy link

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.6.0
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s
  • Are you running Postgres Operator in production? yes
  • Type of issue? feature request

I didn't find a way how to set affinity and tolerations into logical backup cronjob (I didn't count patch the cronjob after it is created). In my opinion, this could be really helpful if I am able to schedule all backup jobs to special node/s for his purpose.
@FxKu FxKu mentioned this issue Jun 3, 2021
Merged
@duckhawk duckhawk mentioned this issue Aug 27, 2022
Merged
@duckhawk
Copy link
Contributor

duckhawk commented Aug 27, 2022 •
edited
Loading

Unfortunately, PR from FxKu didn't solved this problem, so, I created PR with fix

@FxKu FxKu reopened this Aug 30, 2022
@novotnej
Copy link

Hi, can we up the importance of this issue from feature-request to bug? The operator creates cronjobs and inherits the nodeAffinity from configKubernetes.node_readiness_label, but does not inherit the configKubernetes.tolerations - this leads to a situation in our setup, where the cronjob cannot be scheduled anywhere, as our "node_readiness_label" is configured to select tainted nodes...

@FxKu
Copy link
Member

FxKu commented Apr 24, 2024

@novotnej Can you follow up on the PR from @duckhawk and also include nodeAffinity - not only toleration? Same as we did for the pooler.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@duckhawk @novotnej @FxKu @ondrejmichalcik