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.
Before You Begin
Here's a video walk-through.
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
* 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.
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 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.
Before You Begin
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.