Workspaces

A workspace connects repository intent to one cluster namespace, LocalQueue, workload ServiceAccount, and authorization contract.

Single active workspace

TauGrid v0 activates one workspace per cluster. The CLI resolves that workspace from the checked-in connection descriptor or the cluster’s primary-workspace marker, so researchers can omit the workspace name for normal runs.

The active workspace must be Ready before TauGrid submits a workload. Readiness confirms the namespace, queue, workload identity configuration, and authorization contract described in the TauWorkspace reference.

Multiple workspaces

A cluster can contain multiple TauWorkspace objects, but only one is active. The controller marks additional workspaces Degraded with reason AdditionalWorkspaceBlocked and removes their LocalQueue, researcher RoleBinding, and ServiceAccount, leaving the namespace without workspace metadata until promotion.

After the active workspace is deleted and its owned resources are cleaned up, the controller can promote a remaining workspace. This Alpha lifecycle supports controlled, one-at-a-time workspace replacement; concurrent active workspaces and concurrent tenant isolation remain out of scope for this stage.

Platform operators can inspect all workspace objects:

tau workspace list
tau workspace status <name>

Add capacity to the active workspace’s queue, or use a separate cluster, instead of creating a second workspace for concurrent capacity.