17 docs tagged with "operator"

This topic describes how to customize the CR file or the operator deployment.

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.

This topic describes the considerations and requirements for installing multiple instances of Release on the same cluster using custom namespaces.

This section describes how to install the Release application on Amazon EKS.

This section describes how to install the Release application on Azure AKS.

This section describes how to install the Release application on GCP GKE.

This section describes how to install the Release application on Kubernetes On-premise Platform.

This section describes how to install the Release application on an OpenShift cluster on AWS.

This section provides an introduction to Kubernetes Operator as a custom installer to deploy Digital.ai Release.

This topic describes the steps involved in configuring Keycloak before and after the Release installation.

This topic provides a list of the main parameters for the Digital.ai Release Custom Resource (CR).

This topic describes the management of plugins in the operator environment for Release. It covers how plugins are handled within the operator setup, including installation, updates, and configuration.

This section describes how to troubleshoot some of the common issues you may face when installing the Release application using Operator-based installer.

You may want to uninstall the Release Operator to troubleshoot an issue where the Release installation is not working properly, or you no longer want to use the Operator. This section describes the steps to uninstall the Digital.ai Release Operator.

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.

This section describes how to upgrade to the latest Kubernetes Operator-based Release solution on various Kubernetes platforms. The following upgrade scenarios are supported:

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.