Configuration on Kubernetes

📄️ Update Parameters in the CR File or Deployment

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

📄️ Update the Release License—Kubernetes

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.

📄️ Parameters in the CR File

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.

📄️ Customize Your Site—Custom Configuration of Release

Prerequisites

📄️ Select the Type of OIDC Configuration

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

📄️ Configure HTTP2 for Release

This topic illustrates how to configure the settings required to install Release with HTTP2 backend enabled on a Kubernetes cluster.

📄️ Using an External Message Queue

This topic illustrates how to use an external message queue, instead of the RabbitMQ that is provided with the operator itself.

📄️ Using an External Database

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

📄️ Run Diagnostic Mode

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

📄️ Plugin Management using XL CLI

From 23.3 plugin management is possible with XL CLI utility. For more information, see Plugin Manager CLI.

📄️ Manage Plugins Offline in Kubernetes Environment

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

📄️ Configure SSL/TLS in Kubernetes Environment

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.