Installing Qlik Sense Enterprise for elastic deployments

Once you have set up your Kubernetes cluster and prepared your local tools, you are ready to install Qlik Sense Enterprise into your Kubernetes cluster.

To recap, as a minimum before you install you will have:

  • Set up a Kubernetes cluster and added readwritemany storage
  • Prepare your local tools to work with your Kubernetes cluster

The steps below cover the steps to install a first simple install. This includes deploying a MongoDB instance and simple IDP to get you running. To move it to a production ready state, you should review the additional topics for the following areas:

Providing configuration settings

When installing Qlik Sense Enterprise for elastic deployments you can specify settings to the installer in two ways:

  • As parameters in the helm install command.
  • Referencing the settings in a values.yaml and using this in the helm install command.

Storing the configuration settings in a values.yaml allows you to reuse the settings in multiple deployments and add new config sections simply. This can also be version controlled.

Use of a values.yaml file will be used predominately in the Qlik help. You can find more information about YAML files online on sites such as

Installing Qlik Sense

Complete the following steps to install Qlik Sense:

  1. Create a text file called values.yaml.

    1. Add the following content to the file:

      #This setting enables dev mode to include a local MongoDB install devMode: enabled: true #This setting accepts the EULA for the product engine: acceptEULA: "yes"
      If devMode.enabled is set to true, a MongoDB instance is deployed inside of your Qlik Sense Enterprise for elastic deployments in Kubernetes for development and testing purposes only.
    2. Add the following section to accommodate the RBAC security mode in Kubernetes:

      #These settings are to accomodate if RBAC is enabled mira: rbac: create: true serviceAccount: create: true elastic-infra: traefik: rbac: enabled: true nginx-ingress: rbac: create: true
    3. Add the following content to point the services requiring storage to the Kubernetes Persistent Volume claim, update the name of the PVC as needed.

      Observera: If you are using Kubernetes via Docker for Desktop or Minikube then you do not need to have this section
      #These setting specifies the storage for the engine engine: persistence: enabled: true accessMode: ReadWriteMany existingClaim: my-persistent-vol #These setting specifies the storage for the resource-library resource-library: persistence: enabled: true accessMode: ReadWriteMany existingClaim: my-persistent-vol
    4. Save the file.

  2. Run the following command:

    helm install -n qsefe qlik/qsefe -f values.yaml

    The software now starts deploying to the Kubernetes cluster, including downloading all the images and running them.

  3. You can now use kubectl to check the progress. Run the following command:
    kubectl get pods

    If your deployment was successful you will see something similar to this:

    NAME READY STATUS RESTARTS AGE qsefe-collections-7f456595b8-vjhtf 1/1 Running 7 26m qsefe-edge-auth-858f89b849-42z66 2/2 Running 0 26m … (lines removed for brevity)
    It typically takes a few minutes to initialize and show a status of “Running”.
    Tips: If services do not start check the log files of the service for more information. See Viewing logs in Qlik Sense Enterprise for elastic deployments. If the engine or resource library remain in a pending state, check that the Kubernetes cluster has readwritemany storage available as a persistent volume claim and that is it correctly referenced in the YAML.

Accessing the deployment

To connect to the hub and confirm the install you need to obtain the URL for the install inside the Kubernetes cluster. This can vary depending on the configuration and / or vendor but typically you can find the address or IP the install is running on by running the following command:

kubectl describe service qsefe-nginx-ingress-controller

This command returns the address you can add and use to navigate to the hub in your web browser.

You can now connect a Qlik Sense Enterprise for Windows deployment to the cluster and distribute apps to it.

In this simple deployment an example Identity Provider is automatically configured. This allows you to login to the hub with some sample accounts. When you browse to the hub you will be asked to login and you can use the sample account of harley@qlik.example with a password of Password1! .

Observera: The simple IdP is for test purposes only and you should configure a full IdP by reviewing Identity providers in multi-cloud – introduction.

Hjälpte den här informationen?

Varför var informationen inte till hjälp och hur kan vi förbättra den?