Feature Request: NodeAffinity for Operators

[davi5e]

It'd be really nice to use Pod/Node Affinity and Anti-affinity (or at least NodeSelector) to indicate where Pods created by the operator should be scheduled, possibly via a Subscription object.

[ecordell]

Thanks for the suggestion!

Completely agree, and it's on our roadmap. For now there are ways to direct workloads at the namespace level that we've been relying on.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ecordell]

NodeSelector can be used in a subscription's spec.config block to direct workloads at runtime.

[jmhopla]

Hi!,
Not yet any option about nodeAffinity?, NodeSelector is a bit restricting in some use cases.
Thanks,

[dmesser]

@jmhopla what is your use case for setting node affinity on the operator controller pods?

[jmhopla]

Hi @dmesser

Thanks for your time.

The scenario is that we have a OCP cluster with workers in 2 zones or datacenter, we want to use a affinity of preferedbutnotrequired, so we define the pool where we want it to run normally (dc1) but in case of no resources available in dc1, we want that the operator in last effort have the possibility to run in dc2 without manual intervention.

Thanks.