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 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.
Prerequisites
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.
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.
Configuring OIDC is one of the steps in installing or upgrading Digital.ai Release 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
This topic describes the prerequisites, process and considerations for upgrading to the latest version of Release.