-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Che operator should be able to install DevWorkspace and DevWorkspace Che operator #19121
Comments
As we discussed with @l0rd today:
@l0rd please review. |
👍 |
DevWorkspace support also depends on SingleHost (powered by gateway). |
I have added #19142 as a subtask of this epic. |
yes. make sense
|
Here is |
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. |
Is your enhancement related to a problem? Please describe.
Currently the only way to deploy the
DevWorkspac
operator is throughchectl
. When Che is installed from the OperatorHub there is no option to deploy theDevWorkspace
controllers and CRDs.Describe the solution you'd like
Add a new section in
CheCluster
CRD:Other considerations
The default value of
devworkspace.disable
is temporarilytrue
but we should switch tofalse
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
The text was updated successfully, but these errors were encountered: