-
Bug
-
Resolution: Done
-
Critical
-
AMQ 7.9.1.OPR.1.GA
-
None
-
False
-
False
-
User Experience
-
-
-
After deploying some AMQ Brokers on different namespaces, all of them handled by a cluster-wide Operator watching all namespaces. When you restart the Operator pod either by deleting the pod or scaling down and up the Deployment, it triggers the restart of all the AMQ Broker pods in all namespaces.
- relates to
-
ENTMQBR-6057 Installing a cluster-wide Broker operator while Broker pods exist still leads to container restart in Broker pods
- New
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...