This topic illustrates how to configure SSL/TLS with Digital.ai Deploy. 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.
Prerequisites
Prerequisites
Prerequisites
Prerequisites
Prerequisites
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 Deploy or Release using the xl kube install command.
Introduction
Here's what it takes to manage Digital.ai Deploy plugins on a Deploy cluster that was created using the Operator-based installer:
Here is the list of parameters for the Digital.ai Deploy Custom Resource (CR). The following table lists the parameters available in the Digital.ai Deploy's daideploy_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. For more information, see XL Kube Command Reference.
Follow these instructions if you have chosen Keycloak for OIDC authentication.
Configuring OIDC is one of the steps in installing or upgrading Digital.ai Deploy or Release using the Operator-based installer.
If you need to do some customization in the CR file or in the operator deployment, check the following sections.
* Here's a list of questions that you would have to answer to install Digital.ai Deploy or Release using the xl kube upgrade command.
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.