Configuring Additional Installation Values

Last updated: October 21, 2026

Tier Deployment
Enterprise On-Prem

In addition to the YAML files used for Sisense deployment on Linux, Sisense provides an installer-values.yaml file with additional parameters that you can use to customize your deployment.
You can find this YAML file in the following location:
installer/extra_values/installer/installer-values.yaml

Edit this file before you run sisense.sh. The installer reads it together with your configuration file (for example, cluster_config.yaml). Some flags in the table below are not in the file by default; to use them, add them to the file.

To override values of the Helm charts that the installer deploys, use the files in installer/extra_values/helm/. See Using Override Values with Helm Chart Deployments.

Parameters Description
retain_log_files: true Sisense log backup files are stored in: archives/var/log/sisense. The log backup files are deleted if Sisense is uninstalled.
internal_logs: true Fluentd-bit aggregate Sisense service logs are stored on the first kubernetes node.
check_disk_utilization: false When set to true, Sisense validates the second disk performance during installation.
resource_quota: false When set to true, Sisense limits the resource quota limits for the Sisense name space.
resource_quota_limits_cpu: 82 Sets the CPU limits for the Sisense namespace.
resource_quota_limits_memory: 87 Sets the memory limits for the Sisense namespace.
utils_namespace: default The namespace for shared components that the installer deploys, such as the NFS CSI driver, the EFS provisioner, the cluster autoscaler, and the AWS Load Balancer Controller.

install_nginx_gateway_fabric: true

Required for SSL setup. When is_ssl is true or gateway_port is 80, the installer installs NGINX Gateway Fabric, creates the Gateway and the TLS secret, and routes Sisense through it. NGINX Gateway Fabric requires Kubernetes 1.32 or later.

Set to false if you are using a custom ingress controller (or to keep the old nginx ingress controller). With false, the installer does not install NGINX Gateway Fabric or create the TLS secret, and you must expose Sisense yourself.

httpRoute:

  • gatewayName: sisense-gateway

The name of the Gateway.

  • gatewayNamespace: default

The namespace to install NGINX Gateway Fabric and the Gateway in. With SSL, the installer creates the TLS secret sisense-tls in this namespace.

monitoring_namespace: monitoring Specifies a namespace for the monitoring chart.
grafana_port: 30300 The NodePort for Grafana when internal monitoring is installed.
advanced_monitoring: false When set to true, enables advanced monitoring (ControlPlane: etcd, kube-proxy, kube-api, coredns).
prometheus_enabled: true Enables the Prometheus Operator.
annotations.global: Sets the account annotations service for all of the services.
annotations.management: Sets the account annotations service for the management service.
ebs_csi: enabled: false AWS only. Set to true to use the StorageClass ebs-sc (encrypted gp3 volumes, created by the installer) for ReadWriteOnce volumes. The installer installs the AWS EBS CSI driver if it is not already installed. With false (default), the installer uses the gp3 StorageClass.
skip_labeling: false When set to true, the labeling of nodes by the installer is skipped. This is relevant when installing Sisense on an existing Kubernetes cluster, where nodes need to be labeled manually before running installation (node-<namespace>-Application=true, node-<namespace>-Query=true, node-<namespace>-Build=true). On AKS, if the node labels are managed by the node pool, the installer cannot change them: it logs a warning and continues with the existing labels.
label_all_nodes: false Not in the file by default. When set to true, the installer replaces k8s_nodes in your configuration file with all current Kubernetes nodes and gives every node all three roles (application, query, and build).
install_k8s_only: false Single-node and cluster deployments on RKE2 only. When set to true, the installer prepares the servers and installs RKE2, and then exits without installing Sisense. Use this to create a cluster that you then install Sisense on with Helm.
skip_validations: false When set to exactly true or yes, the installer skips its validation checks on the servers of an RKE2 deployment (operating system, kernel, CPU, memory, disk, and ports). This also skips the steps in that stage that stop the host firewall and raise the fs.inotify limits. It also skips the check that each Kubernetes node can run at least 58 pods. Not recommended.
debug_mode: false When set to true, the installer prints every command it runs, for troubleshooting. The output can include passwords from your configuration.
#skip_chown_sisense: false
#chown_sisense_verbose: false
#chown_sisense_dirs_only: false
By default, the installer sets the owner of all files under /opt/sisense to run_as_user:run_as_group. Uncomment and set skip_chown_sisense: true to skip this, chown_sisense_dirs_only: true to change only directories, or chown_sisense_verbose: true to log each change.
azure_csi: enabled: false AKS with storage_type: azurefile only. Set to true to use the Azure Files CSI driver with the StorageClass sisense-azurefile-csi-premium instead of sisense-azurefile-premium. The CSI drivers must be enabled on the AKS cluster; otherwise, the installation stops.
azure_default_disk_size: 1200 AKS only. The size, in GB, of the Azure Files premium share. On Azure, the shared storage volume uses the larger of this value and sisense_disk_size.
efs_rwo: enabled: false With storage_type: efs, set to true to use EFS (StorageClass aws-efs) also for ReadWriteOnce volumes, instead of EBS.
alb_controller:
enabled: false
certificate_arn: ""
annotations: {}
EKS only. Set enabled: true to install the AWS Load Balancer Controller and expose Sisense through an AWS Application Load Balancer. Enter the ARN of your ACM certificate in certificate_arn, and any additional ALB annotations in annotations.