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
feat: Add DevWorkspace as a dependency in che operator #890
Conversation
d9b8db1
to
23eba87
Compare
|
e6c06a5
to
49103d6
Compare
bundle/stable-all-namespaces/eclipse-che-preview-openshift/bundle.Dockerfile
Outdated
Show resolved
Hide resolved
...espaces/eclipse-che-preview-openshift/manifests/che-operator.clusterserviceversion.yaml.diff
Outdated
Show resolved
Hide resolved
...lipse-che-preview-openshift/manifests/org.eclipse.che_chebackupserverconfigurations_crd.yaml
Show resolved
Hide resolved
bundle/stable-all-namespaces/eclipse-che-preview-openshift/metadata/dependencies.yaml
Outdated
Show resolved
Hide resolved
Signed-off-by: Flavius Lacatusu <flacatus@redhat.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was not able to test it precisely but nothing critical found.
Two important things:
- we need to sync on target openshift version.
- I'm not sure if operator should install DWO resources directly, because potentially it can lead to two controllers on the cluster, which would break the stuff.
* To update to stable-all-namespaces channel you need first to remove all subscriptions created for che installed from nightly or stable | ||
channels. IMPORTANT: Removing subscriptions doesn’t mean Eclipse Che operands(che-server, keycloak or roles) will be removed from the cluster. | ||
* DevWorkspace engine will be by default enabled in the new channel. | ||
* In case if you have already installed Che with DevWorkspace engine enabled from channels nightly or stable you need to remove all DevWorkspace resources from the cluster following the next [scripts](https://github.com/devfile/devworkspace-operator/blob/main/build/make/deploy.mk#L77). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what about DevWorkspace Che Operator resources(in devworkpsace-che-operator namespace)? Then also may exist, but I see that it's not really related to the new channel.
FROM scratch | ||
|
||
# Core bundle labels. | ||
LABEL operators.operatorframework.io.bundle.mediatype.v1=registry+v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to sync on which OpenShift versions it's supported.
DWO seems to be available only on OpenShift 4.8+ see here
if lower version is needed - we need to sync how it affects Web Terminals
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agree.
bundle/stable-all-namespaces/eclipse-che-preview-openshift/metadata/dependencies.yaml
Outdated
Show resolved
Hide resolved
@@ -113,6 +116,12 @@ func ReconcileDevWorkspace(deployContext *deploy.DeployContext) (bool, error) { | |||
return true, nil | |||
} | |||
|
|||
// Check if exists devworkspace operator csv is already installed | |||
devWorkspaceOperatorCSVExists := isDevWorkspaceControllerCSVExists(deployContext) | |||
if devWorkspaceOperatorCSVExists { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I understand it means that if you install Che with chectl operator installer, DWO will be installed from resources but not with OLM dependency, which may be unexpected in some corner cases, like when WTO is installed after Che with chectl operator installer.
So, I would say Che on OpenShift should install DWO with olm, or at least into openshift-operators namespace...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, make sense your comments. I think we need to have a dedicate issue for this.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: flacatus, mkuznyetsov, sleshchenko, tolusha The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
/retest |
@flacatus: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
README.md
Outdated
Before installing Eclipse Che using channel `stable-all-namespaces` we need to consider the following: | ||
|
||
* It is not possible to have Eclipse Che installed in single Namespace (currently the default one) and then try to install Che in All Namespace mode using the new channel stable-all-namespaces. | ||
* To update to stable-all-namespaces channel you need first to remove all subscriptions created for che installed from nightly or stable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor: che => Che
Signed-off-by: Flavius Lacatusu <flacatus@redhat.com>
What does this PR do?
Create a new channel to install Che Operator in AllNamespace Mode:
To install Eclipse Che in cluster wide availability after uploading the new bundles for
stable-all-namespaces
we need to go to OperatorHub, select Eclipse Che and then select the new channelstable-all-namespaces
. By default the che operator will be installed in AllNamespace mode and will start to listen for all CheCluster APIS in all cluster.If you already have an Eclipse Che installed from stable/nightly channel and you want to try the new channel you need to consider the following:
It is not possible to have Eclipse Che installed in single Namespace (currently the default one) and then try to install Che in All Namespace mode using the new channel stable-all-namespaces.
To update to stable-all-namespaces channel you need first to remove all subscriptions created for che installed from nightly or stable channels. IMPORTANT: Removing subscriptions doesn’t mean Eclipse Che operands(che-server, keycloak or roles) will be removed from the cluster.
DevWorkspace engine will be by default enabled in the new channel.
In case if you have already installed Che with devWorkspace enabled from channels nightly or stable you need to uninstall DevWorkspace completely from the cluster and then install the Che Operator using stable-all-namespaces channel.
Screenshot/screencast of this PR
What issues does this PR fix or reference?
eclipse-che/che#19891
How to test this PR?
stable-all-namespaces
channel from Operator Hub:Installation Results:
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedReviewers
Reviewers, please comment how you tested the PR when approving it.