Sisense Helm Chart Parameters

This topic details the parameters that can be provided when installing Sisense using the Helm chart directly.

If you want to install Sisense using the Sisense helm chart directly, follow one of the these instructions:

The following is the table of Sisense Helm chart parameters:

Key Type Default Comments

global.applicationDnsName

string

nil

 

global.external_kube_apiserver_address

string

nil

Deprecated, set to save value as global.applicationDnsName

global.cloudLoadBalancer.enabled

bool

false

If using cloud mange k8s (eks/aks/gke) set to true

global.clusterMode.enabled

bool

false

Must be true when installing on multinode/cloud(Otherwise, for Single node installation, keep false)

global.clusterVisibility

bool

true

 

global.deploymentSize

string

"small"

Can be small or large. If you have a small or medium deployment as per the minimum requirements, choose small , otherwise chooselarge.

Define limit values for cpu and memory for Sisense services.

(Can be overridden with <service-name.resources.limits.<resouce>

Example:

Copy 
ai-integration:
  resources:
    limits:
      cpu: 1300m
      memory: 2000Mi
    requests:
      cpu: 100m
      memory: 120Mi

global.enableWidgetDeltas

bool

false

 

global.exposeNodePorts.enabled

bool

false

 

global.gatewayPort

int

30845

 

global.highAvailability

bool

true

 

global.imageRegistry

string

"quay.io/sisense"

 

global.isKubernetesCloud

bool

false

If using cloud mange k8s (eks/aks/gke) set to true

global.isOpenshift

bool

false

If using Openshift set to true

global.kubeNetworkPlugin

string

"calico"

 

global.kubernetesCloudProvider

string

nil

If using cloud mange k8s (eks/aks/gke) set to aws / azure / gcp

global.mongodb.enabled

bool

true

 

global.monitoring.internal

bool

false

If installed Sisense Prometheus, set to true

global.notifyOnUpgrade

bool

true

If true,while Sisense services are still being deployed your Sisense web page will display the maintenance page; once deployment is fully done, the regular Sisense page will display

If false , the Sisense web pages will always be displayed (although some services might be down for a short time, while Sisense services are still being deployed)

global.offlineInstaller

bool

false

 

global.securityContext.fsGroup

int

1000

 

global.securityContext.runAsGroup

int

1000

 

global.securityContext.runAsUser

int

1000

 

global.securityContext.seLinuxOptions.level

string

"s0:c123,c456"

 

global.serviceAccountAnnotations

object

{}

 

global.ssl.enabled

bool

false

 

global.storageClass

string

"<Your RWO StorageClass name>"

For Single node and using node’s file system, set it to manual

Otherwise, Mandatory for Multinode/cloud installation (Example: gp3)

global.storageType

string

"hostPath"

For Single node and using node’s file system, use hostPath

Otherwise, set to empty string or nil

global.vpnMode

bool

false

 

api-gateway.ingress.awsAlb

bool

false

 

api-gateway.ingress.annotations

object

{}

 

api-gateway.ingress.certificateArn

string

nil

 

global.albController.enabled

bool

false

 

grafana.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].key

string

"node-sisense-Application"

Relevant only for Multinode/cloud installation (otherwise, if Single node, leave commented out or removed)

Node affinity to schedule the pods on k8s node with label node-sisense-Application=true

If installed Sisense on a namespace other than sisense, repolace it in the array below from sisense to the correct namespace

(Example: node-mynamespace-Application)

grafana.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].operator

string

"In"

grafana.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].values[0]

string

"true"

grafana.datasources.“datasources.yaml”.apiVersion

int

1

 

grafana.datasources.“datasources.yaml”.datasources[0].access

string

"proxy"

 

grafana.datasources.“datasources.yaml”.datasources[0].isDefault

bool

true

 

grafana.datasources.“datasources.yaml”.datasources[0].name

string

"Prometheus"

 

grafana.datasources.“datasources.yaml”.datasources[0].type

string

"prometheus"

 

grafana.datasources.“datasources.yaml”.datasources[0].url

string

nil

This key/value is commented out, but if Sisense Prometheus is installed, uncomment this key and set the value to http://sisense-prom-operator-kube-prometheus.monitoring:9090

(If Sisense Prometheus is installed on a namespace other than monitoring, replacemonitoring with the correct namespace)

grafana.initChownData.enabled

bool

true

 

grafana.persistence.storageClassName

string

"<Your RWO storageClass name>"

For Single node and using node’s file system, set it to manual

Otherwise, Mandatory for Multinode/Cloud installation (Example: gp3)

grafana.persistence.selectorLabels.app

string

"grafana-sisense"

Must keep for Single node installation.Otherwise, if Multinode/Cloud, remove the entire grafana.persistence.selectorLabels key

If single node and installing Sisense on a different namespace, change it from sisense to the correct namespace
Example: grafana-mynamespace

grafana.securityContext.fsGroup

int

1000

 

grafana.securityContext.runAsGroup

int

1000

 

grafana.securityContext.runAsUser

int

1000

 

grafana.sidecar.dashboards.searchNamespace

string

"sisense"

If installing Sisense on a different namespace, change it here

grafana.sidecar.datasources.createPrometheusReplicasDatasources

bool

false

 

grafana.sidecar.datasources.searchNamespace

string

"sisense"

If installing Sisense on a different namespace, change it here

mongodb.enabled

bool

true

 

mongodb.initContainers[0].command[0]

string

"sh"

 

 

 

The entire mongodb.initContainers is REQUIRED for Single node installation only

Otherwise (if Multinode/Cloud), comment out or remove

mongodb.initContainers[0].command[1]

string

"-c"

mongodb.initContainers[0].command[2]

string

"find /bitnami/mongodb/ -maxdepth 1 -type f -delete; rm -rf /bitnami/mongodb/journal/ /bitnami/mongodb/diagnostic.data/ "

mongodb.initContainers[0].image

string

"quay.io/sisense/utilsbox:stable"

mongodb.initContainers[0].name

string

"init-remove-backup"

mongodb.initContainers[0].volumeMounts[0].mountPath

string

"/bitnami/mongodb"

mongodb.initContainers[0].volumeMounts[0].name

string

"datadir"

mongodb.persistence.size

string

"20Gi"

 

mongodb.containerSecurityContext.runAsUser

int

1000

 

mongodb.pdb.create

bool

false

If Multinode/Cloud, set to true

Otherwise, keep false or commented out

mongodb.persistence.size

string

"20Gi"

 

mongodb.podSecurityContext.fsGroup

int

1000

 

mongodb.metrics.enabled

bool

true

 

Usually commented out

If Sisense Prometheus is installed, uncomment this whole section

If Sisense Prometheus is installed on a namespace other than monitoring, replace the line below from monitoring to the correct namespace)

mongodb.metrics.collector.all

bool

true

mongodb.metrics.compatibleMode

bool

true

mongodb.metrics.extraFlags

string

"--discovering-mode"

mongodb.metrics.serviceMonitor.enabled

bool

true

mongodb.metrics.serviceMonitor.labels.release

string

"sisense-prom-operator"

mongodb.metrics.serviceMonitor.namespace

string

"monitoring"

rabbitmq.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].key

string

"node-sisense-Application"

Relevant only for Multinode/Cloud installation (otherwise, if Single node, leave commented out or removed)

 

Node affinities to schedule the pods on k8s node either with label node-sisense-Application=true or node-sisense-Build=true

 

If Sisense is installed on a namespace other than sisense, replace it in the array below from sisense to the correct namespace

(Example: node-mynamespace-Application)

rabbitmq.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].operator

string

"In"

rabbitmq.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].values[0]

string

"true"

rabbitmq.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[1].matchExpressions[0].key

string

"node-sisense-Build"

rabbitmq.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[1].matchExpressions[0].operator

string

"In"

rabbitmq.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[1].matchExpressions[0].values[0]

string

"true"

sisense-utils.email_sending_block

bool

false

 

sisense-utils.internal_logs

bool

true

 

sisense-utils.isManaged

bool

false

 

sisense-utils.monitoring_namespace

string

"monitoring"

If Sisense Prometheus is installed on a namespace other than monitoring, replace it from monitoring to the correct namespace

sisense-utils.resourceQuota.enabled

bool

false

If set to true, then it will set up the k8s LimitRange and ResourceQuota with default values.

You can override it as follows:

Copy 
sisense-utils:
  resourceQuota:
    enabled: true
    limits_cpu: 82
    limits_memory: 87

(The limits_memory is in Gi units)

sisense-utils.rwxScName

string

"<Your RWX StorageClass name>"

Relevant only for Multinode/Cloud installation (otherwise, if Single node and using node’s file system for data storage, leave commented out, or set to nil)

Mandatory for Multinode/cloud installation (Example: nfs-csi)

sisense-utils.sisenseDiskSize

int

70

 

sisense-utils.timezone

string

"UTC"

 

warehouse.warehouse_dec_graphql_url

string

"https://dec.usw.cloud.sisense.com/graphql"

 

warehouse.warehouse_dec_id

string

"us-west-2.dec.sisense.com"

 

warehouse.warehouse_sels_url

string

"https://auth.cloud.sisense.com"

 

zookeeper.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].key

string

"node-sisense-Application"

Relevant only for Multinode/Cloud installation (otherwise, if Single node, leave commented out or removed)

 

Node affinities to schedule the pods on k8s node either with label node-sisense-Application=true or node-sisense-Build=true

 

If Sisense is installed on a namespace other than sisense, replace it in the array below from sisense to the correct namespace

(Example: node-mynamespace-Application)

zookeeper.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].operator

string

"In"

zookeeper.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].values[0]

string

"true"

zookeeper.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[1].matchExpressions[0].key

string

"node-sisense-Build"

zookeeper.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[1].matchExpressions[0].operator

string

"In"

zookeeper.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[1].matchExpressions[0].values[0]

string

"true"

zookeeper.replicaCount

int

1

For Multinode/Cloud installation, set to 3

(Otherwise, keep it 1 or comment out)

zookeeper.configuration

string
Copy 
tickTime=2000
initLimit=10
syncLimit=5
dataDir=/bitnami/zookeeper/data
clientPort=2181
maxClientCnxns=1000
autopurge.snapRetainCount=3
autopurge.purgeInterval=1
snapshot.trust.empty=true
metricsProvider.className=org.apache.zookeeper.metrics.prometheus.PrometheusMetricsProvider
metricsProvider.httpPort=9141
metricsProvider.exportJvmInfo=true
maxCnxns=0
reconfigEnabled=false
quorumListenOnAllIPs=false
4lw.commands.whitelist=srvr, mntr, ruok
maxSessionTimeout=40000
server.1=sisense-zookeeper-0.sisense-zookeeper-headless.sisense.svc.cluster.local:2888:3888
server.2=sisense-zookeeper-1.sisense-zookeeper-headless.sisense.svc.cluster.local:2888:3888
server.3=sisense-zookeeper-2.sisense-zookeeper-headless.sisense.svc.cluster.local:2888:3888

If installing Sisense on a different namespace, replace in the middle of the server.x strings from sisense to <your-namespace> (there are three locations in each line)

 

Note: For Single node installation, there must be only server.1, without server.2 and server.3

zookeeper.containerSecurityContext.runAsUser

int

1000

 

zookeeper.metrics.enabled

bool

false

If installed Sisense Prometheus, set to true

zookeeper.pdb.maxUnavailable

int

2

Relevant only for Multinode/Cloud installation

Otherwise (for Single node installation), remove or comment out

zookeeper.persistence.size

string

"2Gi"

 

zookeeper.podSecurityContext.fsGroup

int

1000