Checking the Prerequisites

Last updated: October 21, 2026

Tier	Deployment
Enterprise	On-Prem

Below are the prerequisite checks to perform before installing Sisense. Checks marked On the install machine apply to the machine that runs sisense.sh. For the requirements that differ between installation methods, see Choosing an Installation Method.

#	Prerequisite	Adherence Check
1	The server's base OS and the Sisense application must comply. Version compatibility is stated for both the major and minor versions.	Run the following command: `hostnamectl` The results show you the OS, and its major/minor version. Check to ensure compatibility. For example: Operating System: Ubuntu 24.04.1 LTS For the list of prerequisites, see Minimum Requirements for Sisense in Linux Environments.
2	The supported architecture is limited to x86-64/AMD64.	Run the following command: `hostnamectl` The results show you the OS, and its major/minor version. Check to ensure compatibility. For example: Architecture: x86-64
3	A regular (non-root) Linux user that can run `sudo` without a password (NOPASSWD). Where this user is needed depends on the installation method: *On-prem (RKE2) installation with sisense.sh:* A regular (non-root) user with passwordless `sudo` on the install machine and on every server in the cluster (the installer prepares the OS and installs RKE2 on each server over SSH). sisense.sh on an existing cluster (EKS, AKS, GKE, or OpenShift): On the machine that runs sisense.sh, use a regular (non-root) Linux user that can run `sudo` without a password (NOPASSWD) for the duration of the installation; you can remove the NOPASSWD rule afterwards. No privileges are required on the Kubernetes worker nodes: the installer does not connect to or run anything on them. The same user needs `kubectl` access to the cluster with cluster-admin rights. Helm or Provisioner: No Linux user, SSH key, or `sudo` is needed anywhere. Run from any computer with `kubectl` and `helm` and cluster-admin access to the cluster. For on-prem installations, it is recommended that the user has a UID/GID of 1000 (for more information, see Installing RKE with a Specified UID). For details, see Privileges and Permissions for Self-Deployment.	Run the following command: `sudo -l -U <user>` Check that the user has the correct rights. The user must have the right to run ALL as shown below: `(ALL : ALL) NOPASSWD: ALL` If the user cannot run `sudo` without a password, sisense.sh stops with the following errors: User <user> has insufficient sudo permissions sudo configuration should include NOPASSWD for the installation and can be removed at the end of the installation. Also, run the following command to check whether the user is assigned a UID/GID of 1000: `id -u`
4	On the install machine: The Sisense installation directory must be owned by the user used for installing Sisense. So when the package is unpacked, you need to be logged in with the right user. If you run the installation with the wrong root user owning it, you will receive an error such as: The directory '/home/sisense/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag. The directory '/home/sisense/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.	Run the following command: `ls -al` Confirm that all files/directories are owned by the installation user (in the example below, the user name is sisense): drwxr-xr-x 3 sisense sisense 4096 Aug 24 12:50 . drwxrwxr-x 5 sisense sisense 4096 Jul 25 17:32 .. -rw-r--r-- 1 sisense sisense 5836 Jun 14 15:03 cloud_config.yaml -rw-r--r-- 1 sisense sisense 6101 Jun 14 15:03 cluster_config.yaml -rw-r--r-- 1 sisense sisense 7475 Jun 14 15:03 config.yaml drwxr-xr-x 14 sisense sisense 4096 Jun 14 15:03 installer -rw-r--r-- 1 sisense sisense 4918 Jun 14 15:03 openshift_config.yaml -rw-r--r-- 1 sisense sisense 4838 Aug 24 12:52 single_config.yaml -rw-rw-r-- 1 sisense sisense 2037870 Aug 24 13:16 sisense-installer.log -rwxr--r-- 1 sisense sisense 4892 Jun 14 15:03 sisense.sh If the directory is wrongly assigned to the root user, you can either fix the ownership or delete it and unpack the installation package again with the correct installation user logged in. To fix the ownership of the folder to the correct user, run the command: sudo chown -R USER:USER /installation_folder and then confirm correct user ownership with: ls -al
5	On the install machine: Run sisense.sh from the directory that you extracted from the Sisense installation package, not from a copy of the installer source code. The installation package contains files, such as `installer/default.yaml`, that the installer needs.	From the installation directory, run: `ls installer/default.yaml` If the file is missing, the installer stops with the error ERROR: file installer/default.yaml not found. Extract the installation package again.
6	On the install machine: For an upgrade/reinstallation, the same sudo-enabled user account that was used for the previous installation must be used for the new one.	Run the following command: `ls -al /opt/sisense/config` Check that the user that owns the directory is not root.
7	For a single-node installation, the secondary disk must have a permanent mount entry in the `fstab` file.	Run the following command: `sudo lsblk` Check that a second disk shows as mounted. For example: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 250G 0 disk \|-sda1 8:1 0 512M 0 part /boot/efi \|-sda2 8:2 0 1.9G 0 part /boot `-sda3 8:3 0 247.6G 0 part \|-sisense_vg-sisense 253:0 0 87.8G 0 lvm /opt/sisense \|-sisense_vg-root 253:1 0 143.1G 0 lvm / `-sisense_vg-placeholder 253:2 0 16.8G 0 lvm sr0 11:0 1 1024M 0 rom If it is not shown, make sure that the correct entry appears in the `/etc/fstab` file, for example: UUID=2A46-DB7A /boot/efi vfat umask=0077 0 1 /dev/mapper/sisense_vg-sisense /opt/sisense ext4 defaults 0 2 Repeat the procedure for mounting a disk as a prerequisite for single-node installation.
8	If Sisense was uninstalled, the server must be rebooted prior to reinstalling.	After an uninstall, reboot the server on which the new installation is to be performed before performing the new installation. Use the `uptime` command to confirm that the server has rebooted prior to starting the new installation.
9	Avoid installing other applications on the server. If other applications were installed, verify that there are no TCP/UDP port conflicts.	Check that the ports do not conflict with your other applications. Validate that the disabling of the firewall (performed by the Sisense installation) is ok and approved by the customer. You can run the following command to review which ports are in use: `sudo lsof -i -P -n` For the full list of ports, see: Sisense Required Ports for Linux.
10	Sisense must be installed on a clean, dedicated server. Third party components and other non-Sisense capabilities running on the server might conflict with the proper installation and operation of the Sisense platform.	Check that Sisense is installed on a clean server, that is, a server that only had the proper OS installed on it.
11	Sisense can run on one of the compatible OS versions in the list provided. It should not be installed on a modified OS, such as a Kernel that has been specifically modified to harden security, such as applying a CIS (Center for Internet Security) benchmark.	For the list of supported OS versions, Minimum Requirements for Sisense in Linux Environments.
12	If you are installing Sisense on top of an infrastructure that already has Kubernetes installed, make sure that the Kubernetes version that is running is supported for the given Sisense release.	Run the following command to check the Kubernetes version: `kubectl version` See Minimum Requirements for Sisense in Linux Environments.
13	If you are installing Sisense on an existing Kubernetes cluster, each node must have a pod capacity of at least 58 pods.	Run the following command: `kubectl get nodes -o custom-columns=NAME:.metadata.name,PODS:.status.capacity.pods` Check that the PODS value of every node is 58 or higher. The sisense.sh installer stops if a node listed in `k8s_nodes` has a lower capacity. A Helm installation does not check it.
14	If you are installing Sisense on an existing Kubernetes cluster with shared storage, the ReadWriteMany (RWX) StorageClass must work, and a pod that runs as UID 1000 must be able to write to it.	Before you install, create a test PVC with your RWX StorageClass, check that it is bound, and write to it from a test pod that runs as UID 1000 and GID 1000. For the commands, see Storage Requirements for Self-Deployment.

For more information about actions to perform before installing Sisense, watch this video:

Next step:

See Planning Your Configuration.