-
Story
-
Resolution: Not a Bug
-
Major
-
None
-
None
-
None
-
False
-
False
-
Compatibility/Configuration
Not having the possibility to schedule the amq-streams-cluster-operator-xxx pod installed from the OperatorHub where needed, and it impacts the production applications. As soon as the pods start on the wrong nodes within the cluster, the functionality of the operator is broken, resulting in application outages.
Need to add a scheduling functionality option to schedule the operator pod as preferred.