Quickstart
Go from a Workbench-enabled cluster to a running notebook session in under five minutes.
Open Workbench
From the left sidebar, click Workbench. The secondary sidebar opens with a Kubernetes cluster selector at the top and sections for Develop, Compute, Train, Catalog, and Serve.
If your team uses more than one Kubernetes cluster, choose the cluster you want from the selector before creating resources.
Check compute
In Compute > Pools, confirm that at least one pool is available for session workloads. Pools define the node type, autoscaling range, GPU availability, and workload tags that Workbench uses when it schedules sessions and jobs.
Create a session
Go to Develop > Sessions and click New session. The wizard has three steps: Preset, Compute, and Storage.
Pick a preset such as JupyterLab, VS Code, or RStudio, choose an image, choose a pod size, then configure optional storage and Slurm access.
Open it
When the session status changes from Pending to Running, click Open on the row or detail page to launch the notebook or IDE in a new browser tab.
Success looks like this: the session is running, the IDE opens in your browser, and your selected home and data volumes are mounted.
Pause it when you're done
Idle GPUs are billed. Pause the session from the row's overflow menu; your storage stays attached for next time.
Storage persists across pause/resume cycles. Pausing a session releases compute but keeps your home volume and any data volumes you mounted. Resuming the session reattaches them automatically.