43 docs tagged with "operator"

Learn how to manage application images in air-gapped environments. Following are the five different options you can use to ensure your application images are available in air-gapped environments.

Here are some examples how to backup the content of the Release installation on K8s cluster.

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.

From 23.3 version, there are changes how is working answer to the question:

Prerequisites

This topic explains how to enable file logging in the Kubernetes cluster for Release application.

You can install Release in an air-gapped environment disconnected from the public internet. This topic provides information about installing and upgrading Release in such environments using a Minikube cluster and a custom image registry. For other Kubernetes platforms, steps are similar to the ones listed here for Minikube as long as the custom image registry contains all the required images.

Note: Here is a basic setup for the AWS EKS cluster, use it as a guideline to create K8s cluster to have minimal K8s environment for Digital.ai Deploy or Release installation.

Note: Here is a basic setup for the Azure K8S cluster, use it as a guideline to create K8s cluster to have minimal K8s environment for Digital.ai Deploy or Release installation.

Note: Here is a basic setup for the GKE cluster, use it as a guideline to create K8s cluster to have minimal K8s environment for Digital.ai Deploy or Release installation.

Note: Here is a basic setup for the AWS Openshift cluster,

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 a list of questions that you would have to answer to install Digital.ai Release Runner using the xl kube install command.

* Here's a list of questions that you would have to answer to install Digital.ai Release or Runner using the xl kube install command.

Learn how to install and use this product on your Red Hat platform.

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:

PostgreSQL cannot be automatically upgraded during an operator-to-operator or Helm-to-operator upgrade due to incompatible data formats between different PostgreSQL server versions. In such cases, a manual upgrade is necessary. The process involves first backing up the PostgreSQL data, then upgrading to the new PostgreSQL version, and finally restoring the data in the upgraded version.

RabbitMQ during operator2operator upgrade or helm2operator upgrade to version 23.3 of operator will not upgrade automatically to the latest RabbitMQ server version.

This topic illustrates how to set up the persistent volumes on the Release containers.

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 Release Runner. For more information, see XL Kube Command Reference.

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

Follow these instructions if you have chosen Keycloak for OIDC authentication.

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

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

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

This topic illustrates on how to set up the custom context root on the Release.

This topic illustrates on how to set up JVM arguments for Relase containers.

This topic illustrates on how to set up a truststore to store trusted certificates that are used to verify the identities of parties in a secure communication.

In this article, you will learn how to set up a custom image registry to install or upgrade Release. A custom image registry can either be public (not password protected) or private (password protected).

This topic describes how to configure Digital.ai Release on Kubernetes to store reports and task logs on Amazon S3. This setup eliminates the need for persistent volumes, making storage management easier for Kubernetes-based release instances.

If you need to do some customization in the CR file or in the operator deployment, check the 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 upgrade Release or Runner using the xl kube upgrade command.

* Here's a list of questions that you would have to answer to upgrade Digital.ai Release Runner using the xl kube upgrade command.

Patch upgrades from 23.3

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.

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.

If you plan to use an existing message queue — one that is not created by default by the Operator-based installer — you must configure the relevant MQ parameters in the dairelease_cr.yaml file.

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

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

This topic illustrates how to replace the CR values that are in clear-text format in the CR with the secret references.