Loading...

XML

Word

Printable

Type: Story
Resolution: Done
Priority: Major
Fix Version/s: AMQ 7.10.0.OPR.1.GA
Affects Version/s: None
Component/s: operator
Labels:
- more-testing-needed
- upstream-test-coverage

Epic Link:
Broker pod placement
GSS Priority:
Target Release:

AMQ 7.10.0.OPR.1.GA
Upstream Jira:
https://github.com/artemiscloud/activemq-artemis-operator/issues/158
Git Pull Request:
https://github.com/artemiscloud/activemq-artemis-operator/pull/159

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

In the worst-case scenario, all the broker pods may end up on a single node. This will compromise the high availability.

incorporates

ENTMQBR-6578 Allow deployment of each AMQ broker pod in different (AWS) zones

Closed

ENTMQBR-6579 Schedule broker pods to different nodes by default

Closed

is cloned by

ENTMQBR-6408 [doc] Provide an option to specify affinity and anti-affinity in the AMQ Broker operator

Closed

relates to

ENTMQBR-5164 Add NodeSelector functionality with AMQ 7.x broker CR.

Closed

Assignee:: Andy Taylor

Reporter:: Avinash Dongre

Tester:: Roman Vais (Inactive)

Votes:: 5 Vote for this issue

Watchers:: 18 Start watching this issue

Created:: 2020/06/01 6:30 AM

Updated:: 2024/10/01 8:35 PM

Resolved:: 2022/06/03 5:00 PM