Install Workbench
In Alauda AI 2.8.x, Workbench is normally installed and managed by Alauda AI. Enable the workbench component in the cluster-scoped default AmlCluster; you do not need to upload the Workbench Operator package, install the Operator separately, or create a Workbench custom resource manually.
Prerequisites
- Alauda AI is installed on the target cluster. See Install Alauda AI.
- The target cluster has sufficient resources for Workbench workloads.
- Optional: Alauda Service Mesh (Istio) is required only for the Elyra Kubeflow Pipelines run-URL redirect. Istio integration is disabled by default.
Enable Workbench
In Administrator view:
- Open Marketplace > OperatorHub.
- Select the target cluster and open Alauda AI.
- Open the All Instances tab and edit the
defaultAmlClusterinstance. - Set
spec.components.workbench.managementStatetoManaged. - Save the
AmlClusterinstance and wait for Workbench to become ready.
You can apply the component setting in the AmlCluster YAML:
Set spec.components.workbench.values.global.istio.enabled to true only when the target cluster runs Alauda Service Mesh and you need Elyra-generated KFP run URLs to redirect through the Kubeflow Istio ingress gateway.
The default workbench state is Unmanaged, so Workbench is not installed until you explicitly set the component to Managed. For normal deployments, use Managed and let Alauda AI install and reconcile Workbench.
Verification
Check the AmlCluster status:
The resource should report Phase=Ready and Reason=Reconciled. You can also verify the Workbench resources created by Alauda AI:
After the deployment is ready, open Alauda AI and confirm that Workbench appears and that you can open the Workbench list.