Skip to main content

Uninstall the Navin Platform

This page removes the Navin Platform and says what each command keeps. Removing the software never deletes the database nor the settings by itself: deleting them is a separate, explicit step.

danger

The database holds the audit trail of every tenant. Check your retention and legal hold obligations, and take a backup, before you delete it.

OS packages​

  1. Remove the package.

    sudo apt remove navin-platform # Ubuntu
    sudo dnf remove navin-platform # RHEL family
    sudo pacman -R navin-platform # Arch Linux

    The removal stops and disables navin-platform.target, the API, worker, portal and media worker units, and deletes /opt/navin-platform/venv and /var/lib/navin-platform/portal-runtime.

    Kept: /etc/navin-platform (settings), /var/lib/navin-platform (data), /var/log/navin-platform and the database.

  2. Delete the kept data (optional).

    sudo -u postgres dropdb navin_platform
    sudo -u postgres dropuser navin_platform_api
    sudo -u postgres dropuser navin_platform
    sudo rm -rf /etc/navin-platform /var/lib/navin-platform /var/log/navin-platform

    The block that navin-platform-db local added at the top of pg_hba.conf can then be removed.

    Expected result: systemctl list-units 'navin-platform*' lists nothing.

Docker Compose​

CommandEffect
make docker-downRemoves the containers; volumes kept
make docker-cleanRemoves the containers and the volumes (down -v --remove-orphans)

Then delete deploy/compose/.env if you no longer need the local secrets.

Local development with make​

make stop
rm -rf .run

.run holds the pid files, the logs, the PostgreSQL data folder (PG_DATA) and the Keycloak data of make start.

Kubernetes​

  1. Remove the application layer. With Argo CD, delete the Application enterprise-ai of the environment (or the ApplicationSet to remove every layer). Without Argo CD:

    helm uninstall enterprise-ai -n enterprise-ai

    The sandbox namespace is created by the platform bootstrap in GitOps (sandbox.createNamespace: false), so pruning the Application never deletes it.

  2. Remove the data layer (optional). The PersistentVolumeClaims of PostgreSQL, Qdrant, NATS, Redis and ClickHouse follow the reclaim policy of their storage class; the ExternalSecrets use deletionPolicy: Retain, so the Secrets stay until you delete them. The backups in object storage (s3://eai-backups/cnpg, Velero) and the WORM audit archive (object lock in COMPLIANCE mode) are never deleted by an uninstall.

  3. Remove the foundation (optional). tofu destroy in deploy/terraform/envs/<env>.

Verify​

kubectl get all -n enterprise-ai

Expected result: No resources found once the application layer is removed.