Skip to content
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

[WIP] Add docs about using next-all-namespace OLM channel. #2174

Closed
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions modules/administration-guide/nav.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,8 @@

* xref:migration-from-postgresql-9-to-postgresql-13.adoc[]

* xref:switch-che-to-next-all-namespaces-olm-channel.adoc[]

* xref:caching-images-for-faster-workspace-start.adoc[]
** xref:defining-the-list-of-images-to-pull.adoc[]
** xref:defining-the-memory-parameters-for-the-image-puller.adoc[]
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
[id="switch_che-to-next-all-namespaces-olm-channel"]

:navtitle: Swich {prod} to "next-all-namespaces" OLM channel
:keywords: administration-guide, swich-to-next-olm-channel
:page-aliases: .:switch-olm-next-all-namespaces

include::partial$proc_switch_che-to-next-all-namespaces-olm-channel.adoc[]
Original file line number Diff line number Diff line change
@@ -0,0 +1,89 @@
[id="switch_che-to-next-all-namespaces-olm-channel_{context}"]
= Switch {prod} Che to next all namespace OLM channel

{prod} instance installed using OLM can be switched to use "next-all-namespaces" OLM channel for testing new features or bug fixes purpose.

> Alert: {prod} installed from "stable" OLM channel before migration to "next-all-namespace" should be migrated to {devworkspace} engine and this process is not backward compatible.

.Prerequisites

* The `{orch-cli}` tool is available.
* An instance of {prod-short} running in OpenShift 4 cluster.

.Procedure

Make user migration {link} if your previous OLM channel was "stable" or "next".

This comment was marked as outdated.


.Delete current {prod} operator.

Set up namespace "CHE_NAMESPACE" for "stable" or "next" OLM channels:

[source,shell,subs="+attributes"]
----
$ CHE_NAMESPACE="{prod-namespace}"
----

or "openshift-operators" for "tech-preview-stable-all-namespaces" channel:

[source,shell,subs="+attributes"]
----
$ CHE_NAMESPACE="openshift-operators"
----

Delete OLM subscription "{prod-checluster}" and current cluster service version.

[subs="+attributes"]
----
$ SUBSCRIPTION=$(oc get subscription -n ${CHE_NAMESPACE} -o custom-columns=POD:.metadata.name --no-headers | grep eclipse-che)
$ CSV_VERSION_NAME=$(oc get subscription ${SUBSCRIPTION} -n ${CHE_NAMESPACE} -o jsonpath="{.status.currentCSV}")
$ oc delete subscription ${SUBSCRIPTION} -n ${CHE_NAMESPACE}
$ oc delete clusterserviceversion "${CSV_VERSION_NAME}" -n ${CHE_NAMESPACE}
----

.Switch to "tech-preview-stable-all-namespaces" OLM channel.

Create "next" catalog source:

[subs="+quotes,+attributes"]
----
$ oc apply -f - <<EOF
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
name: eclipse-che-next-catalog
namespace: openshift-operators
spec:
image: quay.io/eclipse/eclipse-che-openshift-opm-catalog:next
sourceType: grpc
updateStrategy:
registryPoll:
interval: 5m
EOF
----

Create new subscription for "next-all-namespaces" OLM channel:

[subs="+quotes,+attributes"]
----
$ oc apply -f - <<EOF
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
name: {prod-checluster}
namespace: openshift-operators
spec:
channel: next-all-namespaces
installPlanApproval: Automatic
name: eclipse-che-preview-openshift
source: eclipse-che-next-catalog
sourceNamespace: openshift-operators
EOF
----

Enable single host and {devworkspace} engine in the custom resource:

[subs="+attributes"]
----
$ oc patch checluster/{prod-checluster} -n {prod-namespace} --type=json -p \
'[{"op": "replace", "path": "/spec/devWorkspace/enable", "value": true}, {"op": "replace", "path": "/spec/server/serverExposureStrategy", "value": "single-host"}]'
----