Upgrade
Migrating from the Workbench Cluster Plugin
Starting with v0.2.0, Workbench is delivered as an OLM Helm operator instead of a Cluster Plugin. There is no in-place upgrade between these forms.
-
Back up the existing Workbench resources:
-
In Administrator > Marketplace > Cluster Plugins, uninstall the earlier Workbench cluster plugin. Preserve user PVCs, retained
WorkspaceKindresources, and theaml-workbench-configConfigMap; the operator adopts or reapplies these resources. -
Install the Alauda AI Workbench Operator and create a
Workbenchcustom resource as described in Install Workbench. -
Verify the existing Workspaces and their PVCs are still present, then create and connect to a test Workbench.
If the previous installation relied on the Elyra KFP run-URL redirect, set spec.global.istio.enabled: true in the Workbench custom resource. Istio integration is optional and disabled by default.
Migrating from Kubeflow Notebook
Workbench is NOT compatible with "Kubeflow Notebook" (Alauda AI <= 1.3). You need to create new "workbench" instances, the "Kubeflow Notebook" will be moved to "Advanced - Kubeflow" in the left navigation bar.
We recommend moving to Workbench because "Kubeflow Notebook" will be deprecated in upcoming upstream Kubeflow releases.
You can keep the PVCs used by "Kubeflow Notebook" instances in Alauda AI 1.3. Delete the Notebook instance and mount the PVC into new Workbench instances so data in your Notebook instance remains available. (NOTE Data in the container will be lost, just as when you've used pip install to install packages to the system instead of a virtual environment.)
Procedure
- Log in and open the Alauda AI page.
- Go to Workbench to open the list.
- Click Create and fill in the required fields.
- In Home Directory, select the PVC used by the previous Notebook.