📄️ Plan Your Installation or Upgrade
You use the XL CLI's xl kube command to install or upgrade Digital.ai Deploy or Release or Remote Runner. For more information, see XL Kube Command Reference.
📄️ XL Kube Command Reference
The xl command line tool provides a fast and straightforward method for provisioning Digital.ai Release or Deploy or Remote Runner using YAML files. The YAML files can include items such as releases, pipelines, applications, infrastructure, and target environments.
📄️ Install or Upgrade on Amazon EKS
Prerequisites
📄️ Install or Upgrade on Google GKE
Prerequisites
📄️ Install or Upgrade on Azure AKS
Prerequisites
📄️ Install or Upgrade on Openshift on AWS
Prerequisites
📄️ Install—On-Premise Kubernetes
Important: Use these instructions to install Digital.ai Deploy or Release on a minikube multi-node cluster for testing or illustration purposes. Do not use these instructions to set up a production environment.
📄️ Installation Wizard for Release and Remote Runner
* Here's a list of questions that you would have to answer to install Digital.ai Deploy or Release or Remote Runner using the xl kube install command.
📄️ Install or Upgrade Release on an Air-gapped Kubernetes Cluster
In this article, you will learn how to install or upgrade Release on an air-gapped Kubernetes cluster, providing a step-by-step guide for those who need to install or upgrade Release on a Kubernetes cluster that is disconnected from the internet.
📄️ Upgrade Wizard for Release and Remote Runner
* Here's a list of questions that you would have to answer to install Digital.ai Deploy or Release or Remote Runner using the xl kube upgrade command.
📄️ Select the Type of OIDC Configuration
Configuring OIDC is one of the steps in installing or upgrading Digital.ai Deploy or Release using the Operator-based installer.
📄️ Post Install Keycloak Configuration for Release
Follow these instructions if you have chosen Keycloak for OIDC authentication.
📄️ Configure HTTP2 for Release
This topic illustrates how to configure the settings required to install Release with HTTP2 backend enabled on a Kubernetes cluster.
📄️ Configure SSL/TLS in Kubernetes Environment
This topic illustrates how to configure SSL/TLS with Digital.ai Release. A self-signed certificate is used for illustrative purposes in this procedure. However, you may want to replace it with your own trusted certificate for production environments, which you can do by creating a new Secret object in Kubernetes that contains your certificate and then configuring the ingress controller to use it.
📄️ Update Parameters in the CR File or Deployment
If you need to do some customization in the CR file or in the operator deployment check following sections.
📄️ Update the Release License—Kubernetes
You must use the custom resource definition file (CR file) in case you want to change the Digital.ai Release's license on sites installed using the Operator-based installer.
📄️ Parameters in the CR File
Here is the list of the main parameters for the Digital.ai Release Custom Resource (CR). The following table lists the parameters available in the Digital.ai Release's dairelease_cr.yaml file and their default values.
📄️ Using an Existing PostgreSQL Database
If you plan to use an existing database—one that is not created by default by the Operator-based installer—you must configure the relevant database parameters in the dairelease_cr.yaml file.
📄️ Customize Your Site—Custom Configuration of Release
Prerequisites
📄️ Troubleshoot Install or Upgrade on Kubernetes
Problem: The product is deployed with a wrong property (wrong version, host, etc.)