19 docs tagged with "operator"

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 SSL/TLS with Digital.ai Release. A self-signed certificate is used for illustrative purposes in this procedure. However, you may want to replace it with your own trusted certificate for production environments, which you can do by creating a new Secret object in Kubernetes that contains your certificate and then configuring the ingress controller to use it.

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

* 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:

Here is the list of the main parameters for the Digital.ai Release Custom Resource (CR). The following table lists the parameters available in the Digital.ai Release's dairelease_cr.yaml file and their default values.

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.

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

If you need to do some customization in the CR file or in the operator deployment check following sections.

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.