Minimum Requirements for Sisense in Linux Environments

Last updated: November 5, 2026

Below are descriptions and explanations describing the minimum requirements for Sisense in Linux environments.

Supported Browsers

The Sisense Web Application runs in the following HTML5 supported browsers:

• Microsoft Edge
• Google Chrome
• Firefox
• Safari version 7 and higher - Sisense supports Safari 10 and higher when embedding iFrames.

In order to display Sisense properly, the browser dimensions must be a minimum resolution of 1280px*800px.

The Sisense Web Application also works in mobile phone and tablet browsers that support HTML5. See Viewing Dashboards on Mobile Devices to learn more about mobile compatibility.

Minimum System Requirements

The Sisense Linux deployment is certified to run on the operating systems listed in the table below.

Note the following:

• Sisense only supports x86-64/AMD64 architectures, (for example, ARM64 is not currently supported). You can verify your architecture by running the hostnamectl command in Linux.
• The OS versions specified below are also based on the minor release number, which should be taken into consideration to ensure proper compatibility. (For example, CentOS 8.4 is not currently supported.)
• The OS must be an official release of the given Linux OS, and one that has not been customized (for example, where the OS was modified to harden the kernel).

• SELinux must be disabled on a host node(s), or set to Permissive mode, as Sisense components are managed by k8s on a security context. For more information, see Configure a Security Context for a Pod or Container.

2026 Planned OS/Kubernetes Support

2025 OS/Kubernetes Support

Active OSes

Operating Systems Accepted by the sisense.sh Pre-Flight Check

The sisense.sh installer checks the operating system of the machine it runs on and, for on-prem (RKE2) installations, of every node. If the operating system is not listed in the following table, the installer stops with an Unsupported version has been detected or OS is not supported error.

Install Machine for sisense.sh

The sisense.sh installer runs only on Linux and requires bash 4 or later. There is no macOS, Windows, or PowerShell version of the installer.

• On-prem (RKE2) installations: Run sisense.sh on the first node listed in k8s_nodes in your configuration file. To run it from a separate Linux machine (for example, a bastion host), set remote_installation: true.

• Installations on an existing cluster (EKS, AKS, GKE, or OpenShift): Run sisense.sh on any Linux machine that has kubectl access to the cluster.

• No Linux machine available: Install with the Provisioner or with Helm instead. Both run from any computer that has kubectl and helm. See Choosing an Installation Method.

For the Linux user, sudo, and Kubernetes permissions that each installation method needs, see Privileges and Permissions for Self-Deployment.

Compatibility Matrix

• Cloud Service Providers supported:

  • Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP), and Oracle Cloud Infrastructure (OCI)

• Kubernetes types supported (for pre-built Kubernetes clusters):
  • Amazon Elastic Kubernetes Service (EKS)
  • Google Kubernetes Engine (GKE)
  • Azure Kubernetes Service (AKS)³
  • Red Hat OpenShift
• The final Sisense version that will install/upgrade Kubernetes using RKE1 is L2025.1. Sisense has updated our on-prem deployment process to deploy the Kubernetes cluster using the new RKE2 starting from version L2025.2. For more information, see Changing from RKE1 to RKE2.
  For on-prem installations, Sisense 2026.4 installs RKE2 v1.37.0+rke2r1. On the machine that runs sisense.sh, the installer also installs kubectl v1.37.0 and Helm v3.20.0. Prerequisites for RKE2 v1.37:

  • Kernel version must be 5.13 or newer

  • Your machine must have cgroup v2 (v1 is deprecated)

  • Your machine must support nftables (ipvs is deprecated)

• Sisense on Linux supports Kubernetes versions as detailed in the following table (make sure to see the important footnotes below the table as well):

  Kubernetes Version	1.251,2,3	1.261,2,3	1.271,2,3	1.281,2,3	1.291,2,3	1.301,2,3	1.311,2,3	1.321,2,3	1.331,2,3	1.341,2,3	1.351,2,3	1.361,2,3	1.371,2,3
  Sisense Version
  2026.4	✕	✕	✕	✕	✕	✕	✕	✕	✕	✕	✓	✓	✓
  2026.3	✕	✕	✕	✕	✕	✕	✕	✕	✓	✓	✓	✓	✕
  2026.2	✕	✕	✕	✕	✕	✕	✕	✕	✓	✓	✓	✕	✕
  2026.1	✕	✕	✕	✕	✕	✕	✕	✓	✓	✓	✓	✕	✕
  L2025.4	✕	✕	✕	✕	✕	✕	✕	✓	✓	✓	✕	✕	✕
  L2025.3	✕	✕	✕	✕	✕	✕	✓	✓	✓	✕	✕	✕	✕
  L2025.2	✕	✕	✕	✕	✕	✓	✓	✓	✓	✕	✕	✕	✕
  L2025.1	✕	✕	✕	✕	✓	✓	✓	✕	✕	✕	✕	✕	✕
  L2024.3	✕	✕	✕	✓	✓	✓	✕	✕	✕	✕	✕	✕	✕
  L2024.2	✕	✕	✕	✓	✓	✓	✕	✕	✕	✕	✕	✕	✕
  L2024.1	✓	✓	✓	✓	✓	✕	✕	✕	✕	✕	✕	✕	✕

  ¹ If installing or upgrading to EKS 1.23 or newer, see Creating a Service Account for the EBS CSI Driver on EKS.

  ² GlusterFS has been deprecated in Kubernetes v1.25. Therefore, Sisense does not support GlusterFS storage after Sisense version L2023.4. See this kubernetes blog for more information. Starting with Sisense version L2023.5, for on-prem environments, you must provide NFS storage.

  ³ IMPORTANT: When deploying Sisense on Azure Kubernetes Service (version 1.24 and later) there might be an issue accessing the UI if SSL is enabled. See Deploying Sisense on Azure Kubernetes Service for more information.

  Note: The Sisense Helm chart does not enforce a Kubernetes version. A successful helm install does not mean that your Kubernetes version is supported. Check the table above.

  Note:

  Monitoring is not supported for OpenShift installations and must be disabled (set to false). Consider using OpenShift built-in monitoring tools instead.

Minimum Hardware Requirements

Ensure that your system has at least the following hardware requirements:

• 8 CPUs
• The memory requirements are specified in the recommended deployment sizes table (below)

Recommended Deployment Sizes

The table below describes the minimum requirements for your production deployment. The storage specifications below apply to all supported storage types, unless otherwise indicated. The exact deployment parameters depend on your specific use-case and usage needs.

It is possible for a deployment with machines that have more memory and cores to exceed the large-scale recommendations.

• Your Linux deployment must use AVX2 (also known as Haswell New Instructions). The sisense.sh pre-flight check only detects AVX, so verify AVX2 support yourself, for example with grep -c avx2 /proc/cpuinfo (the result must be greater than 0).
• For cluster deployments that use a shared storage, the following requirements are for the cluster's first three nodes. Each of the first three nodes must have a second unformatted, unmounted, and unpartitioned hard disk with at least 400GB disk space available, plus additional storage for the ElastiCubes.
• For Azure systems that have a 30GB default capacity, you must stop the instance and expand the OS disk capacity up to 300GB before proceeding with installation.
• NVMe disks are recommended for the second disk. If NVMe disks are not used in your system, SSDs are mandatory.
  Sisense does not support systems running with HDD.
• The disk that holds /var/lib/rancher stores the RKE2 container images and etcd. During an on-prem (RKE2) installation, pulling the container images keeps this disk busy for several minutes. If the disk is too slow, etcd stalls and rke2-server restarts, which can make the installation fail. To prevent this, make sure the disk meets the throughput and IOPS requirements above, or put etcd on its own low-latency disk.
• On AWS, EBS gp3 volumes have a baseline of 125MB/s and 3000 IOPS, regardless of the volume size. This is below the requirement for the disk that holds /var/lib/rancher, so you must explicitly provision higher throughput and IOPS for the volume. Do not rely on the burst performance of gp2 volumes, which depends on the volume size and is not sustained.
• For an online installation, the servers must be connected to the internet and must have network access to the Sisense image registry on quay.io (quay.io/sisense_release). If you use your own registry mirror, set it with docker_registry (sisense.sh), global.imageRegistry (Helm), or docker.registry (Provisioner). If you are performing an offline installation, see Installing Sisense in an Offline Environment.
• The network between the servers must reach at least 1 Gbps.
• For on-prem (RKE2) installations with sisense.sh, the installation requires the user/password or SSH key, because the installer connects to every server over SSH. In a multi-node deployment, the same user credentials (password/SSH key) must be defined on all of the server nodes. Installations on an existing cluster (EKS, AKS, GKE, or OpenShift) do not connect to the cluster nodes, and Provisioner and Helm installations need no server credentials. See Privileges and Permissions for Self-Deployment.
• Each Kubernetes node must have a pod capacity of at least 58 pods. To check it, run kubectl get nodes -o custom-columns=NAME:.metadata.name,PODS:.status.capacity.pods. The sisense.sh installer checks every node listed in k8s_nodes and stops if a node has a lower capacity. A Helm installation does not check it. On managed Kubernetes services, the pod capacity of a node depends on its instance type.

What the sisense.sh Pre-Flight Check Enforces

The sisense.sh installer runs the following checks and stops the installation if one of them fails. In an on-prem (RKE2) deployment, the node checks run on every node before Kubernetes is installed. The thresholds below are minimum values that catch undersized machines. They are lower than the recommended deployment sizes above, which you should still follow.

On an existing cluster (EKS, AKS, GKE, or OpenShift), the installer does not run anything on the cluster nodes, so only the install machine checks and the pod capacity check apply. A Helm installation runs none of these checks.

Supported Storage Solutions

The following values of storage_type are available in the sisense.sh installer for multi-node deployments:

• On-Prem HA - nfs, rook-ceph (Rook Ceph on a raw, unpartitioned disk on each node)

• Azure AKS - nfs (Azure NetApp Files), azurefile (AzureFiles from type Premium_LRS). To use the Azure Files CSI driver, also set azure_csi.enabled: true.

• Google GKE - nfs (Filestore)

• Amazon EKS - fsx / efs

• Your own StorageClasses - On any existing cluster, including OpenShift, you can leave storage_type empty and set rwx_sc_name (ReadWriteMany) and rwo_sc_name (ReadWriteOnce) to StorageClasses that already exist in the cluster. The installer checks that both classes exist and does not install a storage driver.

A single-node deployment uses the local disk mounted at /opt/sisense (or /opt).

For the access modes Sisense needs, the StorageClasses to use for each installation method, and how to verify your storage before you install, see Storage Requirements for Self-Deployment.

Open Ports Requirements

Linux outbound ports:

• 443
• 80

The main inbound ports are:

• Sisense web application - TCP 30845 (the default gateway_port), or TCP 443 when SSL is enabled.

• Grafana - TCP 30300, only when internal monitoring is enabled (internal_monitoring: true).

• SSH - TCP 22 from the install machine to every node, only for on-prem (RKE2) installations.

• Between nodes - The Kubernetes (RKE2), etcd, and Calico ports, including TCP 9345 (RKE2 supervisor) in multi-node on-prem clusters.

For the complete list of inbound, outbound, and node-to-node ports, and the conditions under which each one is needed, see Sisense Required Ports for Linux.

Server Connectivity Requirements

For an online installation or upgrade, Sisense reaches a set of external destination hosts (for example, package mirrors, container registries, and Sisense licensing). For the list of destination hosts, and the AI/control-plane connectivity required for GenAI features, see Outbound Connectivity (Destination Hosts) on the Sisense Required Ports for Linux page.

Default Packages Repository

Before installing Sisense, ensure that the default packages repository for your Linux distribution is configured and enabled.

The Sisense installer requires the repository in order to install the following packages:

• python 3
• python3-pip
• nc
• sshpass
• jq
• libselinux-python3
• dbus (for Ubuntu only)

For RHEL/Rocky Linux, access to dl.fedoraproject.org and all its mirrors (cdn.redhat.com network) is required to successfully install all the above packages. (See https://access.redhat.com/articles/1525183.)

Check that the packages repository for your Linux distribution is pre-installed on your server.

sudo apt-get update
sudo DEBIAN_FRONTEND=falseninteractive apt-get install -y gawk python3 netcat-openbsd python3-apt python3-pip dbus pssh sshpass
sudo rm -f /usr/lib/python$(python3 --version | awk '{print $2}' | awk -F '.' '{print $1"."$2}')/EXTERNALLY-MANAGED
sudo python3 -m pip install --upgrade --force-reinstall --ignore-installed pip==21.1.3
sudo ln -sf /usr/local/bin/pip /usr/bin/pip
sudo apt-get install -y jq

sudo yum install -y gawk
sudo amazon-linux-extras install epel -y
sudo amazon-linux-extras install python3.8 -y
sudo ln -sf $(which python3.8) /usr/bin/python3
sudo yum install -y nc jq libselinux-python3 pssh sshpass
sudo python3 -m pip install --upgrade --force-reinstall pip==21.1.3
sudo python3 -m pip install selinux
sudo ln -sf /usr/local/bin/pip /usr/bin/pip
# Enable Docker repo
sudo amazon-linux-extras enable docker=latest

sudo dnf install -y gawk python3 python3-pip python-pip nc jq libselinux-python3 git
sudo python3 -m pip install --upgrade --force-reinstall pip==21.1.3
sudo python3 -m pip install selinux
sudo dnf install -y https://rpmfind.net/linux/fedora/linux/releases/38/Everything/x86_64/os/Packages/s/sshpass-1.09-5.fc38.x86_64.rpm
sudo python3 -m pip install git+https://github.com/lilydjwg/pssh
sudo ln -sf /usr/bin/pip /usr/local/bin/pip

# If Running on Rocky:
pkg_mngr=yum

# If Running on Red Hat:
pkg_mngr=dnf

# Make sure to use correct epel version, examples:
# epel_version=8
# epel_version=9
epel_version=${major_version}

sudo ${pkg_mngr} install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-${epel_version}.noarch.rpm
sudo ${pkg_mngr} install -y --enablerepo="epel" python3.9 python3-pip nc jq libselinux-python3 pssh sshpass
sudo ln -sf $(which python3.9) /usr/bin/python3
sudo python3 -m pip install --upgrade --force-reinstall pip==21.1.3
sudo ln -sf /usr/local/bin/pip /usr/bin/pip
sudo ${pkg_mngr} install -y gawk python3-libselinux
sudo python3 -m pip install configparser zipp

python3 and pip

python3 and pip must be accessible from the terminal via the commands:

• python3
• pip

Verification commands:

sudo python3 -m pip install --upgrade --force-reinstall pip
sudo python3 -m pip install configparser zipp
sudo python3 -m pip install -r installer/requirements.txt --ignore-installed (from the installation folder)

DNS Configuration

The DNS must be configured in the system. This is needed to resolve the Docker registry.

The DNS server must be accessible from the Kubernetes nodes where Sisense is deployed in order for the Sisense component interconnections to function properly.

Whitelisted Resources

The following whitelisted resources must be added:

• cdn.redhat.com (for details, see https://access.redhat.com/articles/1525183)
• pypi.org to install python modules

Next Step

• Checking the Prerequisites