Using Override Values with Helm Chart Deployments

Last updated: October 21, 2026

Tier	Deployment
Enterprise	On-Prem

When you install or upgrade Sisense with the sisense.sh installer, you can override the values that the installer passes to the Sisense Helm chart and to the other Helm charts that it installs. You do this with the override files that are included in the installer package.

Note:

These files are used only by the sisense.sh installer. If you install Sisense with Helm directly, put the same keys in your own values file and pass it to helm install or helm upgrade with -f; see Sisense Helm Chart Parameters. If you install with the Provisioner, see Installing Sisense using Provisioner and Helm.

Helm Override Files

The Helm override files are in the installer/extra_values/helm directory of the installer package. Each file applies to one Helm release:

File	Helm chart it overrides	When the installer applies it
`sisense.yml`	Sisense (the main Sisense chart; the release is named after the Sisense namespace)	Always
`kube-prometheus-stack.yml`	Sisense internal monitoring (Prometheus Operator, release `sisense-prom-operator`)	When internal monitoring is installed (not on OpenShift, and only with cluster visibility)
`logging.yml`	Sisense logging and monitoring chart (release `logmon-<namespace>`)	When internal or external monitoring is enabled (not on OpenShift, and only with cluster visibility)
`nginx-gateway-fabric.yml`	NGINX Gateway Fabric	When `install_nginx_gateway_fabric` is `true` (the default) and SSL is enabled or `gateway_port` is `80`
`alb-controller.yml`	AWS Load Balancer Controller	On AWS, when `alb_controller.enabled` is `true`
`cluster-autoscaler.yml`	Cluster Autoscaler	When `cloud_auto_scaler` is `true` (not on AKS or GKE)
`efs.yml`	EFS provisioner	When `storage_type` is `efs`
`aws-ebs-csi.yml`	AWS EBS CSI driver	On AWS, when the installer installs the EBS CSI driver (it does not install it if the driver already exists in the cluster)
`nfs-csi.yml`	NFS CSI driver	Not applied by the installer in this version: the NFS CSI driver is installed only with values generated from your configuration file

By default, the files are empty or contain only commented-out examples.

How the Installer Applies the Files

The installer passes each override file to Helm after the values that it generates from your configuration file, so a value in the override file takes precedence over the generated value.
For the Sisense release, Helm receives the values in this order: the values generated from your configuration file, then the pod resource limits file for your deployment size (pod-resource-limits-small-deployment-size.yaml or pod-resource-limits-large-deployment-size.yaml, which the installer applies from installer/07_sisense_installation/files), and then sisense.yml. To change resource limits, add them to sisense.yml.
Helm merges maps key by key, but a list in the override file (for example, nodeSelectorTerms, tolerations, or imagePullSecrets) replaces the whole list from the generated values.
The installer does not reuse the values of the previous Helm release. When you upgrade with a new installer package, copy your edited override files into the installer/extra_values directory of the new package before you run sisense.sh; otherwise, your overrides are not applied.

For the keys that you can set in sisense.yml, see Sisense Helm Chart Parameters. The bundled subcharts are named mongodb, rabbitmq, and zookeeper.

sisense.yml Example

The following example sets the number of replicas of three Sisense services, and restricts ZooKeeper, RabbitMQ, and MongoDB to nodes labeled node-sisense-Application=true. Replace sisense in the label key with your Sisense namespace.

In cluster mode, the values that the installer generates for these three services also allow nodes labeled node-<namespace>-Build=true. Because sisense.yml replaces the whole nodeSelectorTerms list, only the Application label remains.

Copy

ERROR: Invalid Code Highlighting Language

Save the file, and then run sisense.sh to install or upgrade Sisense.

Installer Values File

installer/extra_values/installer/installer-values.yaml contains additional installer parameters (not Helm values), for example, internal_logs, monitoring_namespace, alb_controller, azure_csi, azure_default_disk_size, install_nginx_gateway_fabric, and httpRoute.

The installer merges this file with your configuration file (for example, cluster_config.yaml). If a parameter is set in both files, the value in your configuration file is used. See Configuring Additional Installation Values.