-
Bug
-
Resolution: Done
-
Major
-
AMQ 7.2 Image 1.1.GA
-
None
-
2
-
Documentation (Ref Guide, User Guide, etc.)
-
-
+
-
Verified in a release
-
AMQ Broker 1719, AMQ Broker 2019
Unable to create a wildcard route for the management console. It always redirects to the 1st PODS.
Template:- amq-broker-72-persistence-clustered-ssl
As per the documentation [1] section "8.7.4. Creating a route for the management console", we have to create a single route with wildcard policy which will redirect depending on the pod name.
However, I can only connect to ONE pod and its always the 1st POD.
#Result
https://broker-amq-0.broker-amq-headless.amqdemo.svc --> broker-amq-0 https://broker-amq-1.broker-amq-headless.amqdemo.svc --> broker-amq-0 https://broker-amq-2.broker-amq-headless.amqdemo.svc --> broker-amq-0
#Expectation:-
https://broker-amq-0.broker-amq-headless.amqdemo.svc --> broker-amq-0 https://broker-amq-1.broker-amq-headless.amqdemo.svc --> broker-amq-1 https://broker-amq-2.broker-amq-headless.amqdemo.svc --> broker-amq-2
- is cloned by
-
AMQDOC-3092 Document: Unable to create a wildcard route for the management console
- Closed