Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-2336

Unable to create a wildcard route for the management console

XMLWordPrintable

    • 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.

      [1] https://access.redhat.com/documentation/en-us/red_hat_amq/7.2/html-single/deploying_amq_broker_on_openshift_container_platform/index#tutorial-preparing-broker-deployment_broker-ocp

      #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
      

        1. Route.yaml
          0.9 kB
        2. service.yaml
          2 kB

              rhn-support-rkieley Roderick Kieley
              rhn-support-shsingh Shailendra Singh
              Roman Vais Roman Vais (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: