Kubernetes uninstall

Separate application and data-controller removal while preserving volumes, backups, and Secret objects.

Short glossary
  • Helm release: an installed and independently managed resource set from one chart.
  • Secret object: a Kubernetes resource referenced for sensitive values; the delivery charts do not own the values themselves.
  • PersistentVolumeClaim (PVC): a storage request used by a bundled data component.
  • NetworkPolicy: rules governing permitted network connections for application Pods.
  • Container Storage Interface (CSI) and Container Network Interface (CNI) capabilities are provided by the customer cluster.

Safe uninstall

Verify the exact context/namespace, releases, backups and PVCs. First review helm uninstall --dry-run for the application; remove the data release separately only when massaccess-data exists and its data owner authorizes removal.

bash
kubectl config current-context
helm --kube-context "$MA_CONTEXT" list -n "$MA_NAMESPACE"
kubectl --context "$MA_CONTEXT" -n "$MA_NAMESPACE" get pvc
helm --kube-context "$MA_CONTEXT" uninstall massaccess -n "$MA_NAMESPACE" --dry-run
# After reviewing the target and backups:
helm --kube-context "$MA_CONTEXT" uninstall massaccess -n "$MA_NAMESPACE"
# Separately, only if massaccess-data is installed and its removal is approved:
helm --kube-context "$MA_CONTEXT" uninstall massaccess-data -n "$MA_NAMESPACE" --dry-run
helm --kube-context "$MA_CONTEXT" uninstall massaccess-data -n "$MA_NAMESPACE"
WarningRoutine uninstall deliberately has no PVC, PV, snapshot, backup, Secret, or namespace deletion command. Data or identity deletion is a separate explicitly authorized procedure after restore verification and retention approval.