This guide explains how to configure the DNS Time-to-Live (TTL) settings for the Deploy 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.
This guide explains how to manage file system modifications in a Digital.ai Deploy Operator-based installation, including security configurations, volume mounting options, and best practices for handling storage requirements.
The Digital.ai Deploy Helm plugin can deploy and undeploy Helm charts on a Kubernetes host.
This guide explains how to manage Digital.ai Deploy plugins in an offline environment when using a Kubernetes cluster created with the Operator-based installer. You'll learn two approaches to manage plugins when the Deploy UI is not accessible: using Pod Diagnostic Mode or creating a temporary management pod.
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 Deploy.
You must use the custom resource definition file (CR file) in case you want to change the Digital.ai Deploy'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 daideploy_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 daideploy_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 daideploy_cr.yaml file.
This topic illustrates how to use an external database instead of the one that is provided with the operator itself.
If you plan to use an external message queue, instead of the RabbitMQ provided with the operator—you must configure the relevant parameters in the external-mq-patch.yaml file.
This topic illustrates how to replace the CR values that are in clear-text format in the CR with the secret references.