Skip to main content

Qlik Sense Enterprise on Kubernetes enterprise deployment

ON THIS PAGE

Qlik Sense Enterprise on Kubernetes enterprise deployment

The Qlik Sense Enterprise on Kubernetes diagram below shows a larger and more robust deployment example that is adapted to an enterprise that requires near 100% up-time, and that can scale to meet large workloads.

Note: Availability zones can be substituted for update domains or fault domains.

The characteristics of an enterprise Qlik Sense Enterprise on Kubernetes deployment are: 

  • Master/controller nodes distributed across availability zones as needed.
  • Worker nodes distributed across availability zones and replicated within availability zones as needed.
  • Pods are replicated within availability zones and distributed across availability zones as needed.
  • Users are authenticated through the identity provider.
  • Resilient data volumes and MongoDB.

Who should consider this type of Qlik Sense Enterprise on Kubernetes deployment:

  • If you want a highly-available deployment that delivers near 100% up-time.
  • If you expect to support a high volume of users.

Configuration requirements for an enterprise deployment

To successfully set up an enterprise deployment, you should configure your Kubernetes deployment scale both horizontally and vertically as needed. Ultimately, it is up to you how you achieve full scalability to achieve your required level of high-availability. Here are some of the ways you can achieve an enterprise deployment as described above by configuring the Kubernetes autoscalers: 

  • Configure the Kubernetes Horizontal Pod Autoscaler to scale your pods up or down based on custom metrics.
  • Configure the Kubernetes Vertical Pod Autoscaler to allocate more or less resources to pods.
  • Configure the Cluster Autoscaler to allocate or deallocate nodes to the cluster.