Talend Dynamic Engine

Dynamic Engine v1.6.0 introduces major platform capabilities. Maintenance releases v1.6.1 and v1.6.2 deliver targeted stability fixes.

Upcoming changes in v1.7.0

Important:

In R2026-08, Dynamic Engine v1.7.0 introduces two major changes:

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 your deployment plan before upgrading. Guidance to prepare for this change will be available with the R2026-08 release.

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.
Plain Kubernetes manifest deployment with kubectl is no longer supported. The current Classic deployment path cannot be used from v1.7.0 onward.

New features

Feature	Description
Dynamic Engine v1.6.0	Dynamic Engine v1.6.0 is now generally available. Optional persistence mode for Dynamic Engine internal services: Previously, persistent shared storage (such as Amazon EFS or Azure Files) was always required. You can now disable this requirement by setting configuration.persistence.enabled=false on both the dynamic-engine and dynamic-engine-environment Helm charts. Persistent shared storage remains enabled by default in v1.6.0. If you do not modify this setting, the behavior is unchanged. 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. For more information, see the Deploying Dynamic Engine with default network policies. Distroless service images and minimal task images: Set global.profile to minimal to use the distroless variants for Dynamic Engine services and the minimal image for Talend Management Console tasks. Big data Jobs (Spark Batch and Spark Streaming) are incompatible with minimal images and continue to require standard base images. Other Talend Management Console tasks use the minimal image. For more information, see Deploying Dynamic Engine with minimal images Support for Amazon EKS Auto Mode and GKE Autopilot: Dynamic Engine now supports these managed Kubernetes modes. Azure Kubernetes Service (AKS) Automatic is not officially supported. Support for Pod Disruption Budgets: You can now set Pod Disruption Budget rules to keep Dynamic Engine services available during planned maintenance. It reduces the risk of service interruption during cluster changes. For configuration guidance, see Configuring PodDisruptionBudget for Dynamic Engine deployments. 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, Dynamic Engine uses Java 21 to run that task. For deployment and configuration guidance, see the Dynamic Engine Configuration Guide. For a complete list of changes, see Dynamic Engine v1.6.0 detailed changelog.

Feature

Description

Dynamic Engine v1.6.0

Dynamic Engine v1.6.0 is now generally available.

Optional persistence mode for Dynamic Engine internal services: Previously, persistent shared storage (such as Amazon EFS or Azure Files) was always required. You can now disable this requirement by setting configuration.persistence.enabled=false on both the dynamic-engine and dynamic-engine-environment Helm charts.

Persistent shared storage remains enabled by default in v1.6.0. If you do not modify this setting, the behavior is unchanged.
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.

For more information, see the Deploying Dynamic Engine with default network policies.
Distroless service images and minimal task images: Set global.profile to minimal to use the distroless variants for Dynamic Engine services and the minimal image for Talend Management Console tasks.
Big data Jobs (Spark Batch and Spark Streaming) are incompatible with minimal images and continue to require standard base images.

Other Talend Management Console tasks use the minimal image.

For more information, see Deploying Dynamic Engine with minimal images
Support for Amazon EKS Auto Mode and GKE Autopilot: Dynamic Engine now supports these managed Kubernetes modes. Azure Kubernetes Service (AKS) Automatic is not officially supported.
Support for Pod Disruption Budgets: You can now set Pod Disruption Budget rules to keep Dynamic Engine services available during planned maintenance. It reduces the risk of service interruption during cluster changes.

For configuration guidance, see Configuring PodDisruptionBudget for Dynamic Engine deployments.
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, Dynamic Engine uses Java 21 to run that task.

For deployment and configuration guidance, see the Dynamic Engine Configuration Guide. For a complete list of changes, see Dynamic Engine v1.6.0 detailed changelog.

Maintenance releases

Release	Description
Dynamic Engine v1.6.1 changelog	This maintenance release is generally available as of July 9, 2026. It resolves the update issue to v1.6.0 in air-gapped mode and fixes intermittent misfires related to failing registry cleanup Jobs.
Dynamic Engine v1.6.2 changelog	This maintenance release is now generally available. It fixes HTTP(S) proxy support for the S3 client, resolves Route deployment failures when the route-deployer is restarted after more than one hour, and corrects a duplicate registry credential issue that prevented Routes from deploying with a specific image registry configuration.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here