Uninstalling Sisense

Last updated: October 21, 2026

Tier Deployment
Enterprise On-Prem

If you need to remove Sisense, there are several options available to you from the Sisense configuration file (for example, config.yaml, single_config.yaml, cluster_config.yaml, or cloud_config.yaml) you configured when you originally set up Sisense on Linux. You can remove Sisense, remove the Kubernetes cluster, or delete all your Sisense data.

If you installed Sisense with Helm, see Uninstalling a Sisense Helm Installation.

Uninstalling Sisense with the Installer

To remove Sisense, edit the configuration file from the Linux terminal and set any of the following values:

  • uninstall_sisense: Enter true to uninstall Sisense services, but leave your Kubernetes infrastructure in case it's needed in the future. The installer removes the Helm releases that it deployed (Sisense and, where they are enabled, Internal Monitoring, Logging, and NGINX Gateway Fabric). This deletes Sisense, but leaves your Sisense user data and ElastiCube models.

  • uninstall_cluster: Enter true to remove the Kubernetes infrastructure and Sisense services.

    • On an on-premises cluster that the installer created, this uninstalls RKE2 from every server.

    • On a Kubernetes cluster that you manage (for example, Amazon EKS, Azure AKS, Google GKE, or OpenShift), the cluster itself is not removed. The installer removes the cluster services that it added, such as Internal Monitoring and its volumes, and NGINX Gateway Fabric.

  • remove_user_data: Enter true to delete all user data. This deletes your ElastiCube models, application database, message broker, and add-ons: the installer deletes the PersistentVolumeClaims and PersistentVolumes in the Sisense namespace and, on on-premises servers, the Sisense data directories under /opt/sisense. Before it deletes them, the installer saves the logs from /var/log/sisense on each server to /var/log/sisense-log-<timestamp>.tgz.

Note:

remove_user_data has no effect on its own: set it together with uninstall_sisense and/or uninstall_cluster. To remove Sisense completely, enter true for each of the three parameters.

Important:

If you use Rook Ceph storage (storage_type: rook-ceph), uninstall_cluster: true also wipes the block devices that Rook Ceph used on each server (disk_volume_device), even when remove_user_data is false. Back up your data first.

After you edit the configuration file, run the installer with it, and enter y to confirm:

./sisense.sh config.yaml

The uninstallation log is written to sisense-installer.log in the directory from which you ran sisense.sh. For more information about the configuration file, see Installing Sisense on Linux.

Uninstalling a Sisense Helm Installation

If you installed Sisense with Helm, uninstall the releases in the reverse order of installation:

Copy 
# The Sisense namespace and release name (see "helm list -n <namespace>")
NAMESPACE=sisense
RELEASE=sisense

# Logging, if installed
helm uninstall logmon-${NAMESPACE} -n ${NAMESPACE}

# Sisense
helm uninstall ${RELEASE} -n ${NAMESPACE}

# Internal Monitoring, if installed
helm uninstall sisense-prom-operator -n monitoring

  • helm uninstall does not delete the PersistentVolumeClaims that StatefulSets created (for example, for MongoDB, RabbitMQ, and ZooKeeper). To delete the Sisense data as well, delete the remaining PersistentVolumeClaims in the Sisense namespace, and then the namespace. On a single-node installation, the data also remains in the directories under /opt/sisense on the node.

  • helm uninstall does not remove the Prometheus Operator CRDs (*.monitoring.coreos.com). Delete them only if no other application in the cluster uses them.