Set affinity and tolerations to logical backup cronjob

[ondrejmichalcik]

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.

[duckhawk]

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

[novotnej]

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]

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