Skip to main content Skip to complementary content

Dynamic Engine v0.24.0 release

Dynamic Engine v0.24.0 introduces multiple security, reliability, and scalability improvements. In addition, support for Data Services and Routes is now generally available.

Release information

  • Release Name: Dynamic Engine 0.24.0 (2025-09)
  • Release Date: September 24, 2025
  • Compatibility: Kubernetes v1.30 onwards

Upgrade information

This Dynamic Engine 0.24.0 (2025-09) release is a generally available version. This version requires you to redeploy all Data Services and Routes that were deployed in versions prior to 0.24.0.

Before upgrading to 0.24.0, undeploy all Data Services and Routes from Talend Management Console. Failing to undeploy Data Services and Routes prior to the upgrade may lead to unexpected behavior or system failures.
Verify that all Data Services and Routes have been undeployed before starting the upgrade process.
Information noteAttention: Do not use the Redeploy button to undeploy and redeploy. Follow the classic procedure to undeploy all Data Services and Routes, upgrade your Dynamic Engine, and then deploy the Data Services and Routes again.

Notable new feature

  • DPE-1148: Supports custom truststore and keystore for Data Integration Jobs.

Key improvements and security enhancements

  • DPE-1769: Configurable timeouts for bootstrap jobs and Helm installation jobs.
  • DPE-1819: Updates Spring to 3.5.6 (CVE-2025-41248, CVE-2025-41249, CVE-2025-41242).
  • DPE-1785: Updates Netty to 4.1.125.Final (CVE-2025-55163, CVE-2025-58057).
  • DPE-1482: Updates common-lang3 to 3.18.0 (CVE-2025-48924).
  • DPE-1870: Fixes Logback configuration warning (appender layout).

Included services

Installer charts
Helm chart name Chart version Scope Artifact path
dynamic-engine-crd 0.24.0 Custom resource definitions ghcr.io/talend/helm/dynamic-engine-crd
dynamic-engine 0.24.0 Dynamic Engine Infrastructure ghcr.io/talend/helm/dynamic-engine
dynamic-engine-environment 0.24.0 Dynamic Engine environment ghcr.io/talend/helm/dynamic-engine-environment
Services charts
Service Chart version Artifact path
reloader 2.2.3 ghcr.io/talend/helm/reloader
docker-registry 3.0.0 ghcr.io/talend/helm/docker-registry
engine-config-manager 2.2.2 ghcr.io/talend/helm/dpe-engine-config-manager
di-job-deployer 1.19.1 ghcr.io/talend/helm/dpe-di-job-deployer
di-job-controller 1.10.7 ghcr.io/talend/helm/dpe-job-controller
log-collector 1.1.1 ghcr.io/talend/helm/dpe-log-collector
data-service-route-deployer 0.25.2 ghcr.io/talend/helm/dpe-data-service-route-deployer
Services images
Service Image version Function scope Artifact path
engine-operator 0.20.0 Infrastructure ghcr.io/talend/engine-operator
reloader 1.4.8 Infrastructure ghcr.io/talend/reloader
docker-registry 3.0.0 Infrastructure ghcr.io/talend/registry
engine-config-manager 1.6.0 Pairing ghcr.io/talend/engine-config-manager
di-job-deployer 2.20.1 Data integration ghcr.io/talend/di-job-deployer
di-job-controller 2.18.0 Data integration ghcr.io/talend/job-controller
di-job-restore-orphans 1.15.0 Data integration ghcr.io/talend/di-job-restore-orphans
log-collector 1.5.0 Common ghcr.io/talend/dynamic-engine-log-collector
fluent-bit 4.0.10 Common ghcr.io/talend/fluent-bit
data-service-route-deployer 1.6.0 Data Services and Routes ghcr.io/talend/data-service-route-deployer
image-builder 1.5.0 Data Services and Routes ghcr.io/talend/image-builder

Artifact signature checks

Qlik provides digital signatures for all official images and Helm charts from Dynamic Engine v0.22 onwards. All artifacts are signed at build time with an asymmetric key pair: the private key is used for signing, and the public key is made available for signature verification.

For further information about this optional authenticity check of Dynamic Engine artifacts, see Security option: Verifying Dynamic Engine artifact signatures.

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!