Dynamic Engine v0.23.0 release
Dynamic Engine
v0.23.0 introduces an enhanced logging model and security improvements.
Release information
- Release Name: Dynamic Engine 0.23.0 (2025-08)
- Release Date: August 29, 2025
- Compatibility: Kubernetes v1.30 onwards
Key improvements and security enhancements
- DPE-1504: Accepts empty context variables in data integration Jobs.
- DPE-401: Upgrades to OpenJDK 17.0.16_8 to mitigate the Java vulnerability: CVE-2025-50059.
- DPE-1149: Adds initial implementation to enable Dynamic Engine installation on Google Kubernetes Engine (GKE). This is a preparation phase and not intended for production use.
- DPE-1451: Switches to Fluent Bit to load logs of data integration Jobs in batches and forward them in a single request. This improvement replaces the Log4j HttpAppender model, reducing network traffic and improving throughput.
- DPE-1393: Prepares future support for the air-gapped environments, enabling installation in isolated or restricted network environments.
- DPE-1389: Enables updating a data service Job or Route task without undeploying and redeploying the task.
Installer charts
| Helm chart name | Chart version | Scope | Artifact path |
|---|---|---|---|
| dynamic-engine-crd | 0.23.0 | Custom resource definitions | ghcr.io/talend/helm/dynamic-engine-crd |
| dynamic-engine | 0.23.0 | Dynamic Engine Infrastructure | ghcr.io/talend/helm/dynamic-engine |
| dynamic-engine-environment | 0.23.0 | Dynamic Engine environment | ghcr.io/talend/helm/dynamic-engine-environment |
Services charts
| Service | Chart version | Artifact path |
|---|---|---|
| reloader | 2.2.2 | https://stakater.github.io/stakater/reloader |
| docker-registry | 3.0.0 | https://helm.twun.io/docker-registry |
| engine-config-manager | 2.2.1 | 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.2 | ghcr.io/talend/helm/dpe-job-controller |
| log-collector | 1.1.1 | ghcr.io/talend/helm/dpe-log-collector |
| data-service-route-deployer | 0.20.0 | ghcr.io/talend/helm/dpe-data-service-route-deployer |
Services images
| Service | Image Version | Function scope | Artifact path |
|---|---|---|---|
| engine-operator | 0.19.1 | Infrastructure | ghcr.io/talend/engine-operator |
| reloader | 1.4.7 | Infrastructure | ghcr.io/stakater/reloader |
| docker-registry | 3.0.0 | Infrastructure | docker.io/registry |
| engine-config-manager | 1.5.0 | Pairing | ghcr.io/talend/engine-config-manager |
| di-job-deployer | 2.18.1 | Data integration | ghcr.io/talend/di-job-deployer |
| di-job-controller | 2.16.0 | Data integration | ghcr.io/talend/job-controller |
| di-job-restore-orphans | 1.14.0 | Data integration | ghcr.io/talend/di-job-restore-orphans |
| log-collector | 1.4.0 | Common | ghcr.io/talend/dynamic-engine-log-collector |
| data-service-route-deployer | 1.5.1 | Data Services and Routes | ghcr.io/talend/data-service-route-deployer |
| image-builder | 1.4.1 | 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.