Stop and remove Kubernetes

What you will doCopy Anchor Link

Stop sessions before removing the chart, then identify remaining workers, PVCs, Secrets, and hook Jobs.

Before you beginCopy Anchor Link

Confirm the kubectl context, namespace, and Helm release. Prepare database and bucket backups and a list of sessions to stop. Deleting a PVC destroys work that has not been checkpointed.

StepsCopy Anchor Link

1. Stop execution and check dataCopy Anchor Link

Stop accepting new sessions and let active turns finish. Confirm sessions have ended or been checkpointed, and that no workers are running. Stopping the scheduler alone does not stop workers.

2. Remove the chartCopy Anchor Link

helm -n werft uninstall werft

3. Inspect remaining resourcesCopy Anchor Link

helm uninstall leaves these resources behind:

• Worker Pods, nonce Secrets, and workspace PVCs created by the scheduler. Before deleting them, check that sessions have ended (or been checkpointed). Deleting a PVC destroys work that has not been checkpointed. List them with kubectl -n werft get pods,secrets,pvc -l app.kubernetes.io/part-of=werft,werft.installation=<installationId>.
• The migrate and upgrade-check hook Jobs, ExternalSecrets, and Secrets they created (creationPolicy: Orphan). Manually created Secrets also remain. Leftover Jobs do not block the next installation: Helm deletes them before running a hook with the same name. To delete them now, run kubectl -n werft delete job werft-migrate werft-upgrade-check --ignore-not-found.

VerifyCopy Anchor Link

Check that the Helm release and control plane Deployments are gone. Record the remaining worker Pods, nonce Secrets, workspace PVCs, hook Jobs, ExternalSecrets, and user-created Secrets separately. The chart neither creates nor deletes the database or S3 bucket.

TroubleshootingCopy Anchor Link

Removing the scheduler before terminating workers can leave execution and PVCs behind. Keep PVCs if you need their data. Hook Jobs do not block another installation with the same names; the next hook replaces them.

Roll backCopy Anchor Link

Reinstall the exact chart version in the same namespace using the preserved database, Secrets, and bucket. Read the compatibility checks before reinstalling. Reinstalling the chart cannot recover work from a deleted PVC that was never checkpointed.

Next stepsCopy Anchor Link

Install on Kubernetes, Upgrade Kubernetes.