# Talend Dynamic Engine

Dynamic Engine v1.6.0 introduces major platform capabilities. Maintenance releases v1.6.1 through v1.6.3 deliver targeted stability fixes. Maintenance release v1.6.4 adds general availability support for OpenShift (OKD) and fixes a run profile issue that removed Xms/Xmx options.

## Upcoming changes in v1.7.0 (R2026-10)

Information noteImportant:

Dynamic Engine R2026-10 introduces two major changes in v1.7.0:

* configuration.persistence.enabled is set to false by default. After upgrading to v1.7.0, Dynamic Engine no longer requires persistent shared storage for internal services.

  If you currently rely on the default configuration (persistence enabled), review the [v1.7.0 migration procedure](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/dynamic-engine-migration-to-1-7) before upgrading. It includes a separate path for users who already disabled persistence in v1.6.x.

  If you use the internal Docker registry, consider migrating to an external Docker registry before upgrading to v1.7.0. For details on how to connect to an external Docker registry, see [Configuring a custom Docker registry for Talend Management Console tasks](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/configure-docker-registry).

* Plain Kubernetes manifest deployment with kubectl is no longer supported. The current [Classic deployment](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/deploy-with-standard-manifest-files) path cannot be used from v1.7.0 onward.

## New features

| Feature | Description |
| --- | --- |
| Dynamic Engine<br>v1.6.0 | Dynamic Engine<br>v1.6.0 is now generally available.<br><br><ul> <li> <p>Optional persistence mode for <span>Dynamic Engine</span> internal services: Previously, persistent shared storage (such as                              Amazon EFS or Azure Files) was always required. You can now disable                              this requirement by setting                                 <span>configuration.persistence.enabled=false</span> on both                              the <span>dynamic-engine</span> and                                 <span>dynamic-engine-environment</span> Helm charts.</p> <p>Persistent shared storage remains enabled by default in v1.6.0. If you                              do not modify this setting, the behavior is unchanged.</p> </li> <li> <p>Support for Kubernetes Network Policies: You can now enable the                              default network policy set during installation or upgrade, or define                              custom egress rules to restrict outbound traffic.</p> <p>For more information, see the <a href="https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/install-dynamic-engine-with-network-policies" target="_blank">Deploying <span>Dynamic Engine</span> with default network policies</a>.</p> </li> <li>Distroless service images and minimal task images: Set                              <span>global.profile</span> to <span>minimal</span> to use the                           distroless variants for <span>Dynamic Engine</span> services and the minimal image for <span>Talend Management Console</span> tasks.<p>Big data Jobs (<span>Spark Batch</span> and                                 <span>Spark Streaming</span>) are incompatible with                                 <span>minimal</span> images and continue to require                                 <span>standard</span> base images.</p><p>Other <span>Talend Management Console</span> tasks use the minimal image.</p><p>For more information, see <a href="https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/use-minimal-image" target="_blank">Deploying <span>Dynamic Engine</span> with minimal images</a></p></li> <li>Support for Amazon EKS Auto Mode and GKE Autopilot: <span>Dynamic Engine</span> now supports these managed Kubernetes modes. Azure Kubernetes Service                           (AKS) Automatic is not officially supported.</li> <li> <p>Support for Pod Disruption Budgets: You can now set Pod Disruption                              Budget rules to keep <span>Dynamic Engine</span> services available during planned maintenance. It reduces the                              risk of service interruption during cluster changes.</p> <p>For configuration guidance, see <a href="https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/configuring-pod-disruption-budget" target="_blank">Configuring                                 <span>PodDisruptionBudget</span> for <span>Dynamic Engine</span> deployments</a>.</p> </li> <li>Java runtime behavior for tasks: By default, task images use OpenJDK 17                           and OpenJDK JRE 17. If a task artifact is built with Java 21, <span>Dynamic Engine</span> uses Java 21 to run that task.</li> </ul><br><br>For deployment and configuration guidance, see [the Dynamic Engine Configuration Guide](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/). For a complete list of changes, see [Dynamic Engine v1.6.0 detailed changelog](https://help.qlik.com/talend/en-US/dynamic-engine-changelog/Cloud/dynamic-engine-v1-6-0-release-changelog). |
| Dynamic Engine<br>v1.6.4 | General availability support for OpenShift (OKD): You can now deploy<br>Dynamic Engine<br>on an OpenShift cluster, in addition to the existing supported cloud platforms.<br>This capability is available starting with Dynamic Engine<br>v1.6.4.<br><br>For deployment and configuration guidance, see [Configuring OpenShift (OKD) for Dynamic Engine deployment](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/deploying-dynamic-engine-on-openshift). For a complete list of changes, see [Dynamic Engine v1.6.4 detailed changelog](https://help.qlik.com/talend/en-US/dynamic-engine-changelog/Cloud/dynamic-engine-v1-6-4-release-changelog). |

## Maintenance releases

| Release | Description |
| --- | --- |
| [Dynamic Engine<br>v1.6.1 changelog](https://help.qlik.com/talend/en-US/dynamic-engine-changelog/Cloud/dynamic-engine-v1-6-1-release-changelog) | This maintenance release is generally available as of July 9, 2026. It<br>resolves the update issue to v1.6.0 in air-gapped mode and fixes intermittent<br>misfires related to failing registry cleanup Jobs. |
| [Dynamic Engine<br>v1.6.2 changelog](https://help.qlik.com/talend/en-US/dynamic-engine-changelog/Cloud/dynamic-engine-v1-6-2-release-changelog) | This maintenance release is now generally available. It fixes HTTP(S) proxy<br>support for the S3 client, resolves Route deployment failures when the<br>route-deployer is restarted after more than one hour, and<br>corrects a duplicate registry credential issue that prevented Routes from<br>deploying with a specific image registry configuration. |
| [Dynamic Engine<br>v1.6.3 changelog](https://help.qlik.com/talend/en-US/dynamic-engine-changelog/Cloud/dynamic-engine-v1-6-3-release-changelog) | This maintenance release is now generally available. It fixes a memory leak<br>in the dynamic-engine-operator, masks sensitive values in task<br>logs, and sets resource limits for the reloader component. It<br>also fixes ownership of dependent resources created for task execution and<br>preserves the custom truststore/keystore volume during<br>data-service-route-deployer upgrades. |
| [Dynamic Engine<br>v1.6.4 changelog](https://help.qlik.com/talend/en-US/dynamic-engine-changelog/Cloud/dynamic-engine-v1-6-4-release-changelog) | This maintenance release is now generally available. It stops removing the<br>Xms/Xmx options from the run profile. |