# Uninstalling Sisense > If you need to remove Sisense, there are several options available to you from the Sisense config.yaml file you configured when you originally set up Sisense on Linux. You can remove Sisense, remove the Kubernetes cluster, or delete all your Sisense data. *Source: https://docs.sisense.com/main/SisenseLinux/uninstalling-sisense-from-linux.htm* --- Last updated: June 10, 2026 | | | | --- | --- | | [Tier](https://www.sisense.com/pricing/#pricing) | [Deployment](https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-cloud-managed-services.md#ComparisonofManagedCloudandSelfHosted) | | Enterprise | On-Prem | If you need to remove Sisense, there are several options available to you from the Sisense config.yaml file you configured when you originally set up Sisense on Linux. You can remove Sisense, remove the Kubernetes cluster, or delete all your Sisense data. To remove Sisense, you need to edit the config.yaml file from the Linux terminal and modify any of the following values: - **Uninstall\_cluster**: Enter **true** to remove the Kubernetes infrastructure and Sisense services. - **Uninstall\_sisense**: Enter **true** to uninstall Sisense services, but leave your Kubernetes infrastructure in case it's needed in the future. This deletes Sisense, but leaves your Sisense user data and ElastiCube models. - **Remove\_user\_data**: Enter **true** to delete all user data. This deletes your ElastiCube models, application database, message broker, and add-ons. To remove Sisense completely, enter **true** for each of the parameters described above in the config.yaml file. For more information, see [Installing Sisense on Linux](https://docs.sisense.com/main/SisenseLinux/installing-sisense-on-linux.md). **Important:** If you are uninstalling a Sisense cluster with Glusterfs storage, after the uninstallation completes successfully, you must restart the server. **Note:** GlusterFS has been deprecated in Kubernetes v1.25. See for more information.