Description of problem:

The DevSpaces and Web Terminal operators rely on the DevWorkspace operator. When installed in separate namespaces, each operator installs its own instance of DevWorkspace, creating conflicting CustomResourceDefinitions (CRDs).

Prerequisites (if any, like setup, operators/versions):

OCP: 4.15.34
Openshift  DevSpaces Operator: 3.16
Web-terminal operator
Devworkspace operator: v 0.31

Steps to Reproduce:

1. Installing the DevSpaces operator in one namespace will deploy the DevWorkspace operator alongside it.
2. Installing the Web Terminal operator in another namespace will deploy a second DevWorkspace operator.
3. Attempting to create a workspace in this setup will lead to errors due to the conflicting DevWorkspace instances.
 

Error provisioning rbac: rolebindings.rbac.authorization.k8s.io "devworkspace-use-container-build" is forbidden: user "system:serviceaccount:openshift-operators:devworkspace-controller-serviceaccount" (groups=["system:serviceaccounts" "system:serviceaccounts:openshift-operators" "system:authenticated"]) is attempting to grant RBAC permissions not currently held: {APIGroups:["security.openshift.io"], Resources:["securitycontextconstraints"], ResourceNames:["container-build"], Verbs:["use"]}

Note: The error may vary but this is what we could get in one of the scenario where client was trying to create workspace in the Environment. 

Expected results:

To avoid conflicts, if the DevWorkspace operator (DWO) is already present on the cluster, installing another product that depends on DWO—such as Web Terminal or DevSpaces—
should not result in a second DevWorkspace operator instance. Having multiple instances of the DevWorkspace operator leads to workspace creation conflicts and issues for the Web Terminal operator.