This guide explains how to configure the DNS Time-to-Live (TTL) settings for the Release Java Virtual Machine (JVM) in a Kubernetes environment. Proper TTL configuration is crucial for managing how long DNS resolutions are cached, which can affect system performance and network behavior.
When running Digital.ai Release with HTTPS enabled in Kubernetes, you may need to disable the Server Name Indication (SNI) check in certain scenarios. This guide explains how to safely disable the SNI check using Kubernetes commands.
This guide explains how to manage file system operations in Digital.ai Release when using Operator-based installation. By default, containers run with read-only file systems for enhanced security. Learn how to configure various storage options including temporary storage, persistent volumes, and custom mounts to meet your application's needs while maintaining security best practices.
The Helm container plugin allows you simplify the deployment and management of applications on Kubernetes clusters. It allows you to define, install, upgrade, and rollback the Kubernetes applications.
This guide explains how to manage Digital.ai Release plugins in offline mode when working with a Release cluster created using the Operator-based installer. You'll learn multiple approaches to manage plugins when the Release UI is unavailable or not functioning properly.
From 23.3 plugin management is possible with XL CLI utility. For more information, see Plugin Manager CLI.
This topic illustrates how to use the diagnostic mode in Release.
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.
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.
The objective is to illustrate how to use the Helm install and uninstall application workflow in Digital.ai Release to install and uninstall the application using Helm.