Talend Dynamic Engine

Last updated: 10/13/2026

Dynamic Engine v1.7.0 is now available with simpler storage requirements by default and Helm-only deployments.

New features

Feature	Description
Storage persistence	The default installation does not require shared storage. You do not need to set up a persistent distributed storage before installing the engine. You can still configure persistent storage if you need to retain Job data. The embedded image registry does not retain images if its pod restarts. For production deployments, use an external registry. Before upgrading from v1.6.x, see Upgrading to v1.7.0 when persistence is enabled. If you already disabled persistence in v1.6.x, follow the generic upgrade procedure. For fresh-install settings, see Default Helm deployment.
Helm-only deployment	Version 1.7.0 supports Helm deployments only. Existing deployments created with Kubernetes manifests cannot be upgraded in place; moving to Helm requires redeployment.

Feature

Description

Storage persistence

The default installation does not require shared storage. You do not need to set up a persistent distributed storage before installing the engine. You can still configure persistent storage if you need to retain Job data.
The embedded image registry does not retain images if its pod restarts. For production deployments, use an external registry.

Before upgrading from v1.6.x, see Upgrading to v1.7.0 when persistence is enabled. If you already disabled persistence in v1.6.x, follow the generic upgrade procedure. For fresh-install settings, see Default Helm deployment.

Helm-only deployment

Version 1.7.0 supports Helm deployments only. Existing deployments created with Kubernetes manifests cannot be upgraded in place; moving to Helm requires redeployment.

For the complete list of changes in v1.7.0, see the Dynamic Engine v1.7.0 changelog.

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