-
Bug
-
Resolution: Done
-
Major
-
None
-
7.9.0.GA
-
None
In the manual `Deploying AMQ Broker on OpenShift` section [1] it says that:
When a broker Pod in the deployment shuts down due to failure or intentional scaledown of the deployment, the Operator automatically starts a scaledown controller to prepare for message migration. The scaledown controller runs in the same OpenShift project name as the broker cluster.
This is incorrect since in a case of a failure the only expectation is that pod gets restarted.