Decommissioning
This section details the steps to properly uninstall and remove a QALITA platform instance according to the deployment mode used (SaaS, Kubernetes, Docker Compose).
I. SaaS Mode
No technical action is required on the user side. To terminate your account or delete your data:
- Log in to your QALITA SaaS account.
- Go to My Account > Delete My Account.
- Confirm the deletion.
This will result in:
- Deletion of all sources, metrics, and associated packs.
- Removal of user access linked to your organization.
- Automatic revocation of your SaaS license.
This action is irreversible. No data can be recovered after deletion.
II. Kubernetes Deployment
To properly remove QALITA from your Kubernetes cluster:
1. Uninstall with Helm
In the relevant namespace (default: qalita
):
helm uninstall qalita -n qalita
2. Delete Associated Resources
Delete the namespace (⚠️ deletes all resources it contains):
kubectl delete namespace qalita
If you used separate namespaces for SeaweedFS, PostgreSQL, or Redis, delete them as well if necessary.
3. Delete Persistent Volumes (PVC)
Check for remaining volumes:
kubectl get pvc -A | grep qalita
Then delete them:
kubectl delete pvc <pvc-name> -n <namespace>
4. (Optional) Delete Secrets
kubectl delete secret qalita-license -n qalita
Docker Compose Deployment
If you used Docker Compose deployment:
1. Stop and Remove Containers
In the directory where your docker-compose.yaml
is located:
docker-compose down
2. Remove Associated Volumes
docker volume rm qalita_postgres qalita_redis qalita_seaweedfs
(Check exact names with docker volume ls
)
IV. Agent Cleanup
If you installed a QALITA agent (qalita-agent
):
- Remove the agent container or service.
- Delete associated credentials.
- Ensure the agent no longer has scheduled tasks (e.g., cron, systemd, Airflow, etc.).
V. License Revocation
Once the platform is uninstalled, you can request the revocation of your license.
- Contact: support@qalita.io
- Or log in to your customer account to deactivate the license from your dashboard.
VI. Compliance & Sensitive Data
Ensure you have complied with your data management policy:
- Purging logs.
- Deleting database backups.
- Cleaning temporary files (packs, archives, etc.).
QALITA does not retain any data on the publisher side for on-premise deployments.