Skip to content

Deleting Workspaces

Workspaces represent running user jobs with associated environments (e.g., Jupyter or VS Code), resource allocations, and attached volumes. Once a Workspace is no longer needed, you can remove it to free cluster resources. This section provides a detailed overview of the deletion process, including considerations about data integrity and resource cleanup.

1. Prerequisites

  • Workspace Stopped: Verify that the Workspace is not actively running a job or session. If the Workspace is currently active, stop or pause it first to avoid losing unsaved state:

Workspace in Stopped Status

  • Data Backup: Ensure you have saved or backed up important data in a persistent volume (PVC). Ephemeral data inside the Workspace will be lost upon deletion.

2. Deletion Steps

  1. Navigate to the Workspaces Dashboard

    • In the left navigation bar, select the Workspaces Icon Workspaces Icon .
    • You will land on the Workspaces dashboard, which shows all current Workspaces.

    Workspace Dashboard

  2. Select a Workspace

    • Locate the Workspace you want to inspect.

  3. Initiate the Deletion

    • In the Actions column of the desired Workspace card, click the Delete Button Delete button.
    • A Delete Workspace confirmation dialog will appear, prompting you to confirm your selection.

  4. Confirm the Deletion

    • Verify the correct Workspace name is displayed in the dialog.
    • Click Confirm to permanently remove the Workspace from the cluster.
    • If you change your mind or selected the wrong Workspace, choose Cancel to keep it intact.

    Deleting a Workspace Confirmation

  5. Verify Removal

    • Once removed, the Workspace disappears from the dashboard.
    • Any running pods or processes associated with that Workspace are terminated, freeing cluster resources (GPUs, CPUs, memory).

3. Post-Deletion Considerations

  • Associated Volumes: Deleting a Workspace does not automatically remove attached volumes (PVCs). If those volumes are no longer needed, you can delete them from the Storage section.
  • Cleanup Unused Images (Optional): In certain environments, you may also remove unused container images to reclaim storage space on cluster nodes.
  • Historic Logs & Data: Workspace logs stored externally or in persistent volumes remain unaffected; you can review these even after the Workspace is gone.

4. Troubleshooting

  1. Deletion Fails

    • If you encounter errors or the Workspace remains visible, ensure that no processes are actively preventing its termination (e.g., volume or network dependencies).
    • Retry deletion or consult cluster logs.

  2. Workspace Reappears

    • In rare cases, misconfiguration in the control plane or an external scheduler might respawn a Workspace. Double-check that the platform settings no longer include any automated re-creation policies.

  3. Data Loss

    • If you did not save your data to a persistent volume, all unsaved data is lost once the Workspace is removed. This is by design to ensure ephemeral sessions can be quickly terminated without excessive data overhead.

You have now successfully removed an unneeded Workspace. For more advanced use cases (e.g., automating Workspace lifecycle management or scaling ephemeral development environments), refer to the comprehensive Managing Workspaces documentation in the platform’s Administrator Guide.