Sisense and Autoscaling

If your cloud-based Kubernetes deployment supports autoscaling, and you want to dynamically add worker nodes to your Sisense deployment, you need to apply the node labeling strategy as described below so Sisense can add your nodes.

Autoscaling dynamically creates and deletes nodes based on the resource requirements of your pods. As these nodes are created dynamically by your cloud-based Kubernetes, Sisense requirements a specific label format to identify and use them.

Prior to Sisense V8.0 for Linux, the format of the labels was:

Node 1 - nodeApplication=true, nodeQuery=true

Node 2 - nodeApplication=true, nodeQuery=true

Node 3 - nodeBuild=true

The new form from Sisense V8.0 for Linux onwards for node labels is as follows:

Node 1 - node-[NAMESPACE]-Application node-[NAMESPACE]-Query

Node 2 - node-[NAMESPACE]-Application node-[NAMESPACE]-Query

Node 3 - node-[NAMESPACE]-Build

Where [NAMESPACE] is your internal Namespace name for Sisense. The commands below can be used to define how your nodes should be labeled for Sisense to recognize them.

kubectl label node NODE_NAME node-NAMESPACE-Application=true --overwrite

kubectl label node NODE_NAME node-NAMESPACE-Query=true --overwrite

kubectl label node NODE_NAME node-NAMESPACE-Build=true --overwrite