While Operator Life-Cycle Manager (OLM) in OpenShift Container Platform 4 does prevent the installation of strimzi.io Operator and AMQ Streams Operator cluster-scoped it's still possible to install strimzi.io Operator and AMQ Streams Operator when specifying namespace-scoped deployment.

Given that both Operators are sharing common CRDs, ClusterRoles and potentially other objects, this exposes a risk of breaking either the strimzi.io Operator or more important, the AMQ Streams Operator deployment respectively the services it does manage.

Because of that, it's requested to have a warning added to AMQ Streams documentation, advising customers that strimzi.io Operator and AMQ Streams Operator should not be installed on the same OpenShift Cluster as it should generate before mentioned conflicts.

Also Red Hat does not test this scenario, which is why we should further provide warning that a deployment of the two on the same OpenShift Cluster is not recommended and may cause unexpected/undesired harm.