Che operator should be able to install DevWorkspace and DevWorkspace Che operator

[l0rd]

Is your enhancement related to a problem? Please describe.

Currently the only way to deploy the DevWorkspac operator is through chectl. When Che is installed from the OperatorHub there is no option to deploy the DevWorkspace controllers and CRDs.

Describe the solution you'd like

Add a new section in CheCluster CRD:

apiVersion: org.eclipse.che/v1
kind: CheCluster
metadata:
  name: eclipse-che
spec:
(...)
  devworkspace:
    # Deploys the DevWorkspace operator in the cluster.
    # Do nothing if a matching version of the operator is already installed.
    # Fail if a non matching version of the operator is already installed. 
    disable: true

Other considerations

The default value of devworkspace.disable is temporarily true but we should switch to false after a few sprints.

When upgrading a previous installation we should explicitly update the CRD to devworkspace.disable=true.

The DevWorkspace operator won't be in the OperatorHub for a few months. In the context of this issue we should assume that it's not published in the OperatorHub.

Subtasks

• Che Operator should be able to install the Devworkspace operator
• Che Operator should be able to install the Devworkspace Che operator

[sleshchenko]

As we discussed with @l0rd today:

1. Che DevWorkspace Operator should be deployed as well, until it's not fully merged into Che Operator chectl should deploy devworkspace-che-operator when the engine is devworkspace #19001
2. Ideally chectl just reuse Che Operator functionality but don't duplicate logic and apply resources by itself, but that's not requirement.
   For milestone 1, devworkspace should be supported only on OpenShift + OpenShift OAuth.

@l0rd please review.

[l0rd]

@l0rd please review.

👍

[sleshchenko]

DevWorkspace support also depends on SingleHost (powered by gateway).
So, we either should default to SingleHost when DevWorkspace support is enabled or fail if it's not enabled

[l0rd]

I have added #19142 as a subtask of this epic.

[l0rd]

@tolusha I am keeping this issue open as #19142 hasn't been resolved yet.

[tolusha]

yes. make sense
some notes: I've decided to change the fields.
Have disable sounds odd to me since CR is used to enable some features rather than disable.

spec:
  devWorkspace:
    enable: true

[l0rd]

@tolusha I don't know if that's already the case but it would be helpful to add a mention in the docs about it (see the third checkbox in this epic)

[tolusha]

Here is
eclipse-che/che-docs#1895

[l0rd]

I am closing this epic as the linked issues has been closed. I haven't been able to test it though. I have opened a separate issue for that.