Minimum Requirements for Sisense in Linux Environments

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).

2025 Planned OS/Kubernetes Support

2024 OS/Kubernetes Support

Active OSes

Deprecated OSes

Compatibility Matrix

• Kubernetes types supported (for pre-built Kubernetes clusters):
  • Amazon Elastic Kubernetes Service (EKS)
  • Google Cloud Engine
  • Azure Kubernetes Service (AKS)⁴
  • Red Hat OpenShift (see Note below)

• 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.221	1.232	1.242,4	1.252,3,4	1.262,3,4	1.272,3,4	1.282,3,4	1.292,3,4	1.302,3,4
  Sisense Version
  L2024.3	✕	✕	✕	✕	✕	✕	✓	✓	✓
  L2024.2	✕	✕	✕	✕	✕	✕	✓	✓	✓
  L2024.1	✕	✕	✕	✓	✓	✓	✓	✓	✕
  L2023.11	✓	✓	✓	✓	✓	✓	✓	✓	✕
  L2023.9	✓	✓	✓	✓	✓	✓	✕	✕	✕
  L2023.7	✓	✓	✓	✓	✓	✓5	✕	✕	✕
  L2023.6	✓	✓	✓	✓	✓	✓5	✕	✕	✕
  L2023.5	✓	✓	✓	✓	✓	✓5	✕	✕	✕
  L2023.4	✓	✓	✓	✓	✕	✕	✕	✕	✕
  L2023.3	✓	✓	✓	✕	✕	✕	✕	✕	✕
  L2023.2	✓	✓	✓	✕	✕	✕	✕	✕	✕
  L2023.1	✓	✓	✓	✕	✕	✕	✕	✕	✕
  L2022.11	✓	✓	✓	✕	✕	✕	✕	✕	✕
  L2022.10	✓	✓	✓	✕	✕	✕	✕	✕	✕
  L2022.9	✓	✓	✓	✕	✕	✕	✕	✕	✕
  L2022.8	✓	✓	✓	✕	✕	✕	✕	✕	✕
  L2022.7	✓	✕	✕	✕	✕	✕	✕	✕	✕
  L2022.6	✓	✕	✕	✕	✕	✕	✕	✕	✕
  L2022.5	✓	✕	✕	✕	✕	✕	✕	✕	✕
  L2022.4	✓	✕	✕	✕	✕	✕	✕	✕	✕
  L2022.3	✕	✕	✕	✕	✕	✕	✕	✕	✕

  ¹ Kubernetes 1.22 is only supported for RKE or Provisioner installations.

  ² 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.

  ⁵ In some scenarios, application backup & restore may not work as expected. We recommend using snapshot and disk level backups as a workaround for successful restoration with Kubernetes 1.27 support in these versions (L2023.5, L2023.6, L2023.7). We recommend to upgrade to Sisense version L2023.9 or newer, in which backup & restore functionality with Kubernetes 1.27 is fully supported.

  Note:

  Both internal and external monitoring are 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).
• 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. Sisense supplies the following scripts to assist you with expanding the disk capacity:
  • https://data.sisense.com/linux/scripts/sisense_azure_kubespray.sh
  • https://data.sisense.com/linux/scripts/sisense_azure_aks-1.18.sh
• 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.
• AWS disk IOPS is determined by a formula. EBS gets 250MB/s at 3000 IOPS at the peak, but tokens are provided depending on the disk size.
• Servers must be connected to the internet and must have network access to a Docker Hub. 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.
• The installation requires the user/password or SSH key. In a multi-node deployment, the same user credentials (password/SSH key) must be defined on all of the server nodes.
• See Integrating Sisense with Portworx if your environment uses the Portworx platform for end-to-end storage and data management solution on the Kubernetes cluster.
• Set kubernetes_minimum_pods to 58 per node.

Open Ports Requirements

Linux outbound ports:

• 443
• 80

The inbound and outbound ports listed in the table below must be open in the server firewall before installation.

For the Source column in this table:

• Same security group - For an internal cluster, all of the Kubernetes nodes need to open those ports to any other Kubernetes nodes within the cluster.

• Customer IP Address - The ports should be accessible from outside the cluster in order to use the application. The customer can set the IP scope level, that is, who is able to access the network.

Server Connectivity Requirements

The servers must be connected to the Internet and must have network access to the following server list:

• apt.dockerproject.org
• archive.ubuntu.com
• auth.cloud.sisense.com
• bitbucket.org
• bugs.launchpad.net
• dl.fedoraproject.org
• docs.docker.com
• docs.helm.sh
• download.docker.com
• github.com
• gcr.io
• github.com
• grafana.com
• help.ubuntu.com
• index.docker.io
• kubernetes.io
• l.sisense.com
• mirror.centos.org
• ppa.launchpad.net
• pypi.python.org
• quay.io
• registry-1.docker.io
• storage.googleapis.com
• www.ubuntu.com
• yum.dockerproject.org

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/Centos/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 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 CentOS/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