Configure the JDK Version for Release on Kubernetes

This guide is for administrators who run Digital.ai Release on an operator-based (Kubernetes) installation. It describes how to select the JDK version by setting the container image tag. For JVM-based (installer) installations, see Configure the JDK Version for Release.

On operator-based installations, the JDK is determined by the container image, not by the wrapper configuration file. The default Release server image tags run on JDK 21. To run the Release server on JDK 25, use the image tag with the -jdk25 suffix.

Set the image tag in the custom resource (CR), the same field you use for a patch upgrade:

kubectl patch -n digitalai digitalaireleases.xlr.digital.ai dai-xlr \
  --type=merge --patch '{"spec": {"image": {"tag": "26.3.x-jdk25"}}}'

The operator restarts the Release pods automatically after the update. For more information about setting the image tag, see Upgrade Patch Version of the Release.

The -jdk25 image is preconfigured for JDK 25 and does not include the Java Security Manager settings, so you do not need to edit the wrapper configuration file. Script security on JDK 25 is enforced through sandbox configuration settings. For more information, see Configure Script Security.

note

Release Runner does not have a -jdk25 image. Only the Release server image is available in both JDK 21 and JDK 25 variants.