This document provides procedures for backing up the Digital.ai Release installation on a Kubernetes (K8s) cluster. Follow these steps to ensure your data and configuration are protected before performing upgrades or maintenance.
This topic illustrates how to configure the settings required to install Release with HTTP2 backend enabled on a Kubernetes cluster.
Before You Begin
This guide explains how custom resource keys are migrated during the Digital.ai Release operator upgrade process. Understanding this process is crucial for maintaining your configuration when upgrading to newer versions of the operator.
Here's a video walk-through.
You can install Release on an air-gapped environment disconnected from the public internet. This topic provides information about installing and upgrading Release in such environments using a Minikube cluster and a custom image registry. For other Kubernetes platforms, steps are similar to the ones listed here for Minikube as long as the custom image registry contains all the required images.
Note: Here is a basic setup for the AWS EKS cluster, use it as a guideline to create K8s cluster to have minimal K8s environment for Digital.ai Deploy or Release installation.
Note: Here is a basic setup for the Azure K8S cluster, use it as a guideline to create K8s cluster to have minimal K8s environment for Digital.ai Deploy or Release installation.
Note: Here is a basic setup for the GKE cluster, use it as a guideline to create K8s cluster to have minimal K8s environment for Digital.ai Deploy or Release installation.
Note: Here is a basic setup for the AWS Openshift cluster,
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.
* Here's a list of questions that you would have to answer to install Digital.ai Release Remote Runner using the xl kube install command.
* Here's a list of questions that you would have to answer to install Digital.ai Release or Remote Runner using the xl kube install command.
The Release Kubernetes plugin allows user to connect to different K8s clusters using Kubectl and perform operations. The plugin also allows the user to lookup Kube Contexts from a config file that the user provides and connect to a specific cluster from a list of configs.
The Release Kubernetes plugin allows Release to work with resources on a Kubernetes host.
Here's what it takes to manage Digital.ai Release plugins, if Release is not working on a Release cluster that was created using the Operator-based installer:
Postgresql during operator2operator upgrade or helm2operator upgrade will not upgrade automatically to the latest server version
RabbitMQ during operator2operator upgrade or helm2operator upgrade to version 23.3 of operator will not upgrade automatically to the latest RabbitMQ server version.
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.
From 23.3 plugin management is possible with XL CLI utility. For more information, see Plugin Manager CLI.
Before You Begin
This topic illustrates how to use the diagnostic mode in Release.
Configuring OIDC is one of the steps in installing or upgrading Digital.ai Release using the Operator-based installer.
In this article, you will learn how to set up a custom image registry to install or upgrade Release. A custom image registry can either be public (not password protected) or private (password protected).
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.
* Here's a list of questions that you would have to answer to upgrade Release or Remote Runner using the xl kube upgrade command.
* Here's a list of questions that you would have to answer to upgrade Digital.ai Release Remote Runner using the xl kube upgrade command.
Patch upgrades from 23.3
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.
If you plan to use an existing message queue — one that is not created by default by the Operator-based installer — you must configure the relevant MQ parameters in the dairelease_cr.yaml file.
This topic illustrates how to use an external database instead of the one that is provided with the operator itself.
This topic illustrates how to use an external message queue, instead of the RabbitMQ that is provided with the operator itself.