Migrating from IBM Wazi for Dev Spaces

To migrate from IBM® Wazi for Dev Spaces to Red Hat® OpenShift® Dev Spaces on the same cluster, completely delete the existing Wazi deployment before you can deploy Red Hat's Dev Spaces as these two cannot be co-installed on the same cluster. This documentation details the steps to uninstall IBM Wazi for Dev Spaces 4.0.0 provided by IBM.

Prerequisites

  1. Log in to your OpenShift® cluster web console as a cluster administrator.

  2. An active oc session with administrative permissions to the destination OpenShift Cluster.

  3. dsc the command line tool for Red Hat OpenShift Dev Spaces.

Procedure using the command line

  1. Commit and push all the necessary changes to the Git repository from your Wazi for Dev Spaces workspace to prevent any data loss during the removal process. Backup important files like Zowe™ team configuration files for users with Zowe projects in persistent storage if required.

  2. To validate if there are any Dev Spaces containers present on the Cluster, click the Hamburger icon on the upper-right of the OpenShift web console, select Observe in the sidebar and choose Metrics. Ensure the value of count returned is 0, when the expression count(container_processes{namespace=~'.+-devspaces\\W\\w+', container=~'wazi'}) is run in the query bar, ensure no one is using an active workspace.

  3. Login into the cluster using the oc login command and run dsc server:delete --delete-all. Proceed with caution as this command uninstalls the Wazi for Dev Spaces and Dev Workspace operators, delete Webhooks, delete devworkspaces.workspace.devfile.io resources, delete the devworkspace-operator-fast-redhat-operators-openshift-marketplace subscription, and remove all other workloads, services, subscriptions, RBAC, ImageContentSourcePolicy and other resources linked to the Dev Spaces operator.

  4. The Wazi License CR has to be manually deleted in the workspace installation namespace, you can run this command with the oc client oc delete WaziLicense wazi-devspaces-license. Then run the command oc delete crd WaziLicense to get rid of the License CRD.

  5. Uninstall the operator by unsubscribing the operator to the openshift operator namespace using oc get subscription ibm-wazi-code -n openshift-operators -o yaml | grep currentCSV to get the currentCSV name. Then delete the current subscription using oc delete subscription ibm-wazi-code -n openshift-operators.

  6. Delete the Cluster Service Version using the CSV name retrieved from the previous step using oc delete clusterserviceversion <currentCSV> -n openshift-operators.

IBM Wazi for Dev Spaces is uninstalled and you can install Redhat Openshift Dev Spaces.

Procedure using the OpenShift console

  1. Navigate to the openshift-operators namespace using the projects dropdown in the Administrator section. Click on Operators in the side menu and select installed operators under the drop down. The two operators are IBM Wazi for Dev Spaces 4.0.0 provided by IBM and the Dev Workspace operator 0.31.2 provided by Red Hat.

  2. Click on the IBM Wazi for Dev Spaces Operator, navigate to the all-instances tab on the top of the console. Delete all the custom resources listed. Two resources that are often present for an active workspace are the wazi-devspaces CR of type CheCluster and the wazi-devspaces-license of type WaziLicense. To delete, click the ellipsis icon on the right of wazi-devspaces row and select Delete CheCluster. For wazi devspaces license select delete WaziLicense.

  3. After the custom resources are deleted, to delete the operator click the kebab menu on the right of IBM Wazi for Dev Spaces row in the Install Operator page.

  4. Click on the Dev Workspace Operator in the installed operators page. Navigate to the all-instances tab. Delete all the custom resources listed.

  5. Unsubscribe the operator to the openshift-operators namespace. Follow the steps below to uninstall the IBM Wazi for Dev Spaces Operator and Red Hat DevWorkspace Operator(delete subscription).

    1. Expand the Operators menu on the left and click Installed Operators.

    2. Click the three dots at the side of IBM Wazi for Dev Spaces and choose uninstall operator. Give it some time until the Operators are uninstalled.

  6. The Wazi License Custom Resource Definition remains on the cluster. Take these steps to delete the Wazi License CRD:

    1. Expand the Home menu on the left and click Search. Type the keyword CRD in the search bar.

    2. Scroll down to the bottom and delete the CRD with name Wazi License of type org.eclipse.che.

  7. To ensure your cluster is not utilized, if any unnecessary resources delete all the projects or namespaces with devspaces-[uid] appended to them e.g: john-doe-ibm-com-devspaces-i74n78.

IBM Wazi for Dev Spaces is uninstalled and you can install Redhat Openshift Dev Spaces.

Troubleshooting

If there is an issue pertaining to delete any workspace related resources. Remove the dependant finalizers and ensure it does not block the deletion of dependant resources.

Last Updated:
Contributors: PETER HAUMER, phaumer, Gagan Hegde, Esther M, Swathi Sadananda