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

Re-check the current context, namespace, releases, and PVC inventory before every action. Run each command without --apply first and review the plan. Remove the data release separately and only when massaccess-data is actually installed.

bash

./bin/massaccess-k8s uninstall \
  --release application \
  --namespace <namespace>

./bin/massaccess-k8s uninstall \
  --release application \
  --namespace <namespace> \
  --namespace-ack <namespace> \
  --apply

./bin/massaccess-k8s uninstall \
  --release data \
  --data-release-ack massaccess-data \
  --namespace <namespace>

./bin/massaccess-k8s uninstall \
  --release data \
  --data-release-ack massaccess-data \
  --namespace <namespace> \
  --namespace-ack <namespace> \
  --apply

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.