Adding the Starburst license

Use kubernetes secrets to add the Starburst license to your cluster.

In this guide, you will learn how to add the Starburst license to your cluster. You will use a Kubernetes secret to store the license.

Getting the Starburst license

Contact your Starburst representative or customer support team to get the Starburst Enterprise license. This is required to run Starburst Enterprise on Kubernetes.

Create the file

Name the license file provided to you starburstdata.license. Place this in a safe place that is accessible to the Kubernetes cluster or in the same directory as the Starburst helm charts.

Create the secret

A Kubernetes Secret is a resource used to store sensitive data, such as passwords, OAuth tokens, and SSH keys, in a secure and controlled way. Secrets are stored in Kubernetes' etcd database, typically encoded with Base64.

This is what is reccomneded for storing the Starburst license and can be executed by using the following kubectl command to create the secret:

bash

kubectl create secret generic starburstlicense --from-file=starburstdata.license

Add the license to the sep-prod-setup.yaml

The kuberentes secret now needs to be added to you sep-prod-setup.yaml file. Add the following line to the sep-prod-setup.yaml file:

yaml

starburstPlatformLicense: starburstlicense

The entire file now looks like this:

yaml

starburstPlatformLicense: starburstlicense

environment: %ENVIRONMENT_NAME%
sharedSecret: %SHARED_SECRET%

coordinator:
  resources:
    memory: "%GB_AMOUNT%"
    requests:
      cpu: %CPU_AMOUNT%

  # This affinity will ensure the coordinator and worker are deployed in the sep node group.
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
          - matchExpressions:
              - key: apps
                operator: In
                values:
                  - sep

worker:
  resources:
    memory: "%GB_AMOUNT%"
    requests:
      cpu: %CPU_AMOUNT%

  # This affinity will ensure the coordinator and worker are deployed in the sep node group.
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
          - matchExpressions:
              - key: apps
                operator: In
                values:
                  - sep

Reference Building the YAML file for more information on the sep-prod-setup.yaml file.