-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
AMQ 7.11.0.GA
-
False
-
None
-
False
-
-
-
Important
When trying to expose AMQ Broker via creation of an Ingress, the ingress is successfully created, but it appears no underlying route is created to hook the ingress to the broker. Connecting to the exposed ingress hostname and port with a client results in timeouts waiting to obtain the cluster topology. Connecting to the ingress with an AMQP client results in a " AMQP SASL header mismatch value 48, expecting 41. In state: HEADER0" error message.
So far attempts to expose the broker with plain connectors, ssl termination (edge) and ssl passthrough don't seem to be working.
- links to
-
RHSA-2024:129921 AMQ Broker 7.12.0.OPR.1.GA Container Images Release