Configure Http2 for Release
This topic illustrates how to configure the settings required to install Release with HTTP2 backend enabled on a Kubernetes cluster.
This topic illustrates how to configure the settings required to install Release with HTTP2 backend enabled on a Kubernetes cluster.
Prerequisites
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.
Prerequisites
Prerequisites
Prerequisites
Prerequisites
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.
* 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.
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 what it takes to manage Digital.ai Release plugins on a Release cluster that was created using the Operator-based installer:
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.
Follow these instructions if you have chosen Keycloak for OIDC authentication.
This topic describes how to set up Release in a production environment. It describes how to configure the product, environment, and server resources to get the most out of the product. This document is structured in three sections:
Configuring OIDC is one of the steps in installing or upgrading Digital.ai Deploy or Release using the Operator-based installer.
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 install Digital.ai Deploy or Release or Remote Runner using the xl kube upgrade command.
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.
The xl command line tool provides a fast and straightforward method for provisioning Digital.ai Release, Deploy, and Remote 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.