Skip to main content
Removing a workspace means tearing down its Kubernetes resources and the AWS resources created for it, in roughly the reverse order of deployment.
Deleting a workspace is irreversible. It removes the workspace’s clusters, catalog registrations, and the metadata stored in its S3 bucket. Confirm the workspace is no longer in use before you begin.

Step 1: Remove the workspace components

Delete the workspace custom resources by re-rendering the chart and deleting what it produced (or delete the NamespaceConfig and QueryRouter directly):

Step 2: Remove the workspace NodePool and namespace

Karpenter terminates the workspace’s nodes once the NodePool is gone and no pods remain.

Step 3: Remove the Pod Identity associations

Step 4: Remove the workspace IAM roles

Delete the inline policies, then the roles:

Step 5: Remove the metadata bucket

This removes one workspace. The shared cluster components (EKS, Karpenter, the ALB Controller, cert-manager, the e6-operator) remain in place to serve other workspaces. Remove those only if you are decommissioning the entire EKS cluster.

See also

Last modified on September 29, 2026