-
Story
-
Resolution: Not a Bug
-
Major
-
None
-
None
-
False
-
None
-
False
Currently, there is no anti-affinity rule and all broker pods can end up on one node.
There is an improvement scheduled for 7.10 https://issues.redhat.com/browse/ENTMQBR-3622 but this is only to permit modification to add manually the anti-affinity rule.
Shouldn't this (one pod = one node) be done by default when more than one broker pod is deployed?
- is incorporated by
-
ENTMQBR-3622 Provide an option to specify affinity and anti-affinity in the AMQ Broker operator
- Closed