Using Override Values with Helm Chart Deployments
  • 18 May 2022
  • 1 Minute to read
  • Contributors
  • Dark
    Light
  • PDF

Using Override Values with Helm Chart Deployments

  • Dark
    Light
  • PDF

In addition to the YAML files used for Sisense deployment on Linux, Sisense includes the following YAML files for installing Sisense using Helm charts and changing the configuration of the pods in the deployment.
You can use these files for the deployment of different helm charts for your environment.
You can find these Helm Chart YAML files in kubespray\extra_values\helm.
The files for the Helm Chart types are:

  • alb-controller.yml

  • cluster-autoscaler.yml

  • cluster-metrics.yml

  • descheduler.yml

  • logging.yml

  • nfs-client.yml

  • nfs-server.yml

  • nginx-ingress.yml

  • prometheus-operator.yml

  • sisense.yml
    descheduler.yml file example
    The following example shows the settings you would enter for the descheduler.yml file, which is used for the descheduler helm chart.
    schedule: "*/15 * * * *"

  • sisense.yml file example

The following example shows the settings you would enter for the sisense.yml file, which is used for the Sisense major helm chart.

oxygen:
   replicaCount: 3
api-gateway:
   replicaCount: 6
pivot2-be:
   replicaCount: 6
identity:
   replicaCount: 6
galaxy:
   replicaCount: 6
query:
   replicaCount: 3
translation:
   replicaCount: 3
zookeeper:
 affinity:				
   nodeAffinity:
	 requiredDuringSchedulingIgnoredDuringExecution:
		nodeSelectorTerms:
			- matchExpressions
			  - key: "node-sisense-Application"
			    operator: In
			    values:
			    - "true"
rabbitmq-ha:
 affinity:				
   nodeAffinity:
     requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
            - matchExpressions
			  - key: "node-sisense-Application"
				operator: In
				values:
				- "true"
mongodb-replicaset:
 affinity:				
   nodeAffinity:
     requiredDuringSchedulingIgnoredDuringExecution:
       nodeSelectorTerms:
           - matchExpressions
             - key: "node-sisense-Application"
				operator: In
				values:
				- "true"

After you have added any target values, be sure to save the file.
Under the same directory, there are two additional YAML files for setting the pod resource based on the size of your deployment.

  • pod-resource-limits-large-deployment-size.yaml
  • pod-resource-limits-small-deployment-size.yaml

You can customize the settings to match your deployment requirements and save the file.


Was this article helpful?