Dynamic Engine v1.4.0 release
Dynamic Engine
v1.4.0 improves pod scheduling flexibility with Kubernetes tolerations
and includes critical security and stability updates.
Release information
- Release Name: Dynamic Engine 1.4.0 (2026-03)
- Release Date: March 26, 2026
- Compatibility: Kubernetes v1.30 and above
Key improvements and fixes
- DPE-2603: Fixed HTTP proxy environment variables being interpreted as commands in data-service, route, and run scripts
- DPE-2482: Deactivated service account on Route pods and Jobs
Notable new features
| Feature | Description | Ticket |
|---|---|---|
| Tolerations | Added support for Kubernetes tolerations, enabling pods to be scheduled on tainted nodes. | DPE-2631 |
Included services
| Helm chart name | Chart version | Scope | Artifact path |
|---|---|---|---|
| dynamic-engine-crd | 1.4.0 | Custom resource definitions | ghcr.io/talend/helm/dynamic-engine-crd |
| dynamic-engine | 1.4.0 | Dynamic Engine Infrastructure | ghcr.io/talend/helm/dynamic-engine |
| dynamic-engine-environment | 1.4.0 | Dynamic Engine environment | ghcr.io/talend/helm/dynamic-engine-environment |
| Service | Chart version | Artifact path |
|---|---|---|
| reloader | 2.2.8 | ghcr.io/talend/helm/reloader |
| docker-registry | 3.0.0 | ghcr.io/talend/helm/docker-registry |
| engine-config-manager | 2.10.0 | ghcr.io/talend/helm/dpe-engine-config-manager |
| di-job-deployer | 1.29.0 | ghcr.io/talend/helm/dpe-di-job-deployer |
| di-job-controller | 1.19.0 | ghcr.io/talend/helm/dpe-job-controller |
| log-collector | 1.9.0 | ghcr.io/talend/helm/dpe-log-collector |
| data-service-route-deployer | 1.11.0 | ghcr.io/talend/helm/dpe-data-service-route-deployer |
| metrics-agent | 0.1.8 | ghcr.io/talend/helm/dpe-metrics-agent |
| metrics-config-manager | 0.1.7 | ghcr.io/talend/helm/dpe-metrics-config-manager |
| Service | Image version | Feature | Artifact path |
|---|---|---|---|
| engine-operator | 1.5.0 | Infrastructure | ghcr.io/talend/engine-operator |
| reloader | v1.4.13 | Infrastructure | ghcr.io/talend/reloader |
| docker-registry | 3.0.0 | Infrastructure | ghcr.io/talend/registry |
| engine-config-manager | 1.13.0 | Pairing | ghcr.io/talend/engine-config-manager |
| di-job-deployer | 2.26.0 | Data integration | ghcr.io/talend/di-job-deployer |
| di-job-controller | 2.24.2 | Data integration | ghcr.io/talend/job-controller |
| di-job-restore-orphans | 1.21.0 | Data integration | ghcr.io/talend/di-job-restore-orphans |
| log-collector | 1.11.0 | Common | ghcr.io/talend/dynamic-engine-log-collector |
| fluent-bit | 4.2.2 | Common | ghcr.io/talend/fluent-bit |
| data-service-route-deployer | 1.13.0 | Data Services and Routes | ghcr.io/talend/data-service-route-deployer |
| image-builder | 1.11.0 | Data Services and Routes | ghcr.io/talend/image-builder |
| metrics-agent | 0.1.0 | Metrics | ghcr.io/talend/dynamic-engine-metrics-agent |
| metrics-config-manager | 0.1.0 | Metrics | ghcr.io/talend/dynamic-engine-metrics-config-manager |
Artifact signature verification
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.