34 docs tagged with "install"

Learn how to manage application images in air-gapped environments. Following are the five different options you can use to ensure your application images are available in air-gapped environments.

Here are some examples how to backup the content of the Deploy installation on K8s cluster.

From 23.3 version, there are changes how is working answer to the question:

Prerequisites

You can install Deploy in an air-gapped environment that is disconnected from the public internet. This guide provides information for installing and upgrading Deploy in such environments using a Minikube cluster and a custom image registry. While these steps are tailored for Minikube, they can be adapted to other Kubernetes platforms, provided the custom image registry contains all the necessary 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,

This topic describes the system requirements, installation, and syntax for the XL Command Line Interface (XL CLI) used to support Digital.ai DevOps as Code and blueprints features.

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 Deploy using the xl kube install command.

Learn how to install and use this product on your Red Hat platform.

Introduction

Here's what it takes to manage Digital.ai Deploy plugins, if Deploy master is not working, on a Deploy cluster that was created using the Operator-based installer:

PostgreSQL cannot be automatically upgraded during an operator-to-operator or Helm-to-operator upgrade due to incompatible data formats between different PostgreSQL server versions. In such cases, a manual upgrade is necessary. The process involves first backing up the PostgreSQL data, then upgrading to the new PostgreSQL version, and finally restoring the data in the upgraded 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 Release 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.

Follow these instructions if you have chosen Keycloak for OIDC authentication.

This topic illustrates how to use the diagnostic mode in Deploy.

Configuring OIDC is one of the steps in installing or upgrading Digital.ai Deploy using the Operator-based installer.

Configuring OIDC is one of the steps in installing or upgrading Digital.ai Deploy or 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 Deploy's license on sites installed using the Operator-based installer.

* Here's a list of questions that you would have to answer to upgrade Digital.ai Deploy 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 daideploy_cr.yaml file.

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 daideploy_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 daideploy_cr.yaml file.

This topic illustrates how to use an external database instead of the one that is provided with the operator itself.

If you plan to use an external message queue, instead of the RabbitMQ provided with the operator—you must configure the relevant parameters in the external-mq-patch.yaml file.

This topic illustrates how to replace the CR values that are in clear-text format in the CR with the secret references.

The xl command line tool provides a fast and straightforward method for provisioning Digital.ai Release, Deploy, and Runner servers using YAML files. The YAML files can include items such as releases, pipelines, applications, infrastructure, and target environments. In addition, the XL CLI is used for installing or upgrading Digital.ai Deploy and Release.