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.
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.
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.
Problem: The product is deployed with a wrong property (wrong version, host, etc.)
Problem: The product is deployed with a wrong property (wrong version, host, etc.)
This topic describes how to troubleshoot the Release service.
If you need to do some customization in the CR file or in the operator deployment, check the following sections.