This guide will walk you through the process of deploying a Digital.ai Deploy Docker image to an Kubernetes on-premise cluster using a Helm chart.

This helm chart automates and simplifies deploying and managing Digital.ai Deploy on an Kubernetes on-premise cluster by providing the essential features you need to keep your clusters up and running.

Intended audience

  • Administrators and DevOps with a working knowledge of Docker, Kubernetes, and Helm.
  • Digital.ai Deploy users with an understanding of Deploy concepts

In this guide

  1. What are we going to install?
  2. Before you begin
  3. Parameters
  4. Installation
  5. Upgrade
  6. Best practices
  7. Troubleshooting
  8. Using an exisitng DB
  9. Using an existingMQ
  10. Configuring SSL/TLS
  11. Sample values.yaml file

What are we going to install?

The Helm chart installs the following components:

  1. A single instance / pod of PostgreSQL database
  2. The RabbitMQ in highly available configuration
  3. The HAProxy Ingress Controller
  4. Digital.ai Deploy Masters and Workers in a highly available configuration

Note: We recommend that you use an external PostgreSQL (e.g. CrunchyData PostgreSQL operator) instance, for production grade installations. See configuring the CrunchyData PostgreSQL operator for more details.


Some important considerations

  • The minimum version of Digital.ai Deploy that is supported for the Deploy Helm chart is 9.6 or higher.
  • You must configure the support for a Persistent Volume (PV) provisioner such as the Network File System (NFS) in the underlying infrastructure along with a desired StorageClass, which you plan to use with Digital.ai Deploy.
  • You will need a license file for Digital.ai Deploy in the base64 encoded format.
  • You will need a repository Keystorefile in the base64 encoded format. For more information on keystore, see this article.

Images and repositories we use

Next Step