Dynamic Engine v0.22.0 release
Dynamic Engine
v0.22.0 introduces support for Dynamic Engine
customization with Helm values, new Beta features for Data Services and Routes, and
Dynamic Engine
specific artifact signature validation.
Release information
- Release Name: Dynamic Engine 0.22.0 (R2025-06)
- Release Date: June 30, 2025
- Compatibility: Kubernetes v1.30 onwards
Installation recommendation
- Recommended: Use the Helm-based deployment procedure to leverage enhanced deployment customization capabilities. See (Recommended) Helm deployment.
- Classic: The installation procedure kubectl, based on plain Kubernetes manifests, is still fully supported. See Kubectl deployment
Upgrade information
No breaking changes have been introduced. Standard upgrade procedure is supported.
New custom resources definitions have been adopted to enable Dynamic Engine customization use cases. A migration process automatically converts old custom resources to the new format, that is to say, QlikRuntimeInfra to DynamicEngine, and QlikRuntime to DynamicEngineEnvironment, respectively.
Notable new features
| Features | Description |
|---|---|
| DPE-1191 | Enforces schema validation on Dynamic Engine charts and enables custom values validation. |
| DPE-1069 | Adds a README file in the Helm archive with custom installation instructions. |
| DPE-888 | Enables namespace renaming for Dynamic Engine and Dynamic Engine environments. |
| DPE-1162 | Allows declaring a specific custom storage class for Dynamic Engine PVCs (PersistentVolumeClaim). |
| DPE-917 | Allows defining custom keys in a custom keystore for Job artifact signature validation. |
| Features | Description |
|---|---|
| DPE-1074 | Adds connection parameters for Data Services and Routes tasks. |
| DPE-1128 | Adds run profiles for Data Services and Routes tasks. |
| DPE-1053 | Defines a fixed number of replicas for each Route deployment at the environment level. |
| DPE-1171 | Configures Horizontal Pod Autoscaling for each Route deployment at the environment level. |
| DPE-1058 | Reports workload error status on Talend Management Console task status, for example, when a Route is unable to start. |
Key improvements
- DPE-920: Dynamic Engine environment becomes idle after two days without running data integration Jobs.
- DPE-477: Adds label selector to retrieve service pods when too many pods from executed Jobs are present.
- DPE-1328: Fixes an issue where service job-controller can fail to start correctly on minikube.
Included services
| Helm chart name | Chart version | Scope | Artifact path |
|---|---|---|---|
| dynamic-engine-crd | 0.22 | Custom resource definitions | ghcr.io/talend/helm/dynamic-engine-crd |
| dynamic-engine | 0.22 | Dynamic Engine Infrastructure | ghcr.io/talend/helm/dynamic-engine |
| dynamic-engine-environment | 0.22 | Dynamic Engine environment | ghcr.io/talend/helm/dynamic-engine-environment |
| Service | Chart version | Artifact path |
|---|---|---|
| reloader | 1.3.0 | https://stakater.github.io/stakater/reloader |
| docker-registry | 2.2.3 | https://helm.twun.io/docker-registry |
| engine-config-manager | 2.0.0 | https://talend.github.io/helm-charts-public/engine/dpe-engine-config-manager |
| di-job-deployer | 1.16.1 | https://talend.github.io/helm-charts-public/engine/dpe-di-job-deployer |
| di-job-controller | 1.7.2 | https://talend.github.io/helm-charts-public/engine/dpe-job-controller |
| log-collector | 1.0.1 | https://talend.github.io/helm-charts-public/engine/dpe-log-collector |
| data-service-route-deployer | 0.14.2 | https://talend.github.io/helm-charts-public/engine/dpe-data-service-route-deployer |
| Service | Image version | Function scope | Artifact path |
|---|---|---|---|
| engine-operator | 0.18.0 | Infrastructure | ghcr.io/talend/engine-operator |
| reloader | 1.3.0 | Infrastructure | ghcr.io/stakater/reloader |
| docker-registry | 2.8.1 | Infrastructure | docker.io/registry |
| engine-config-manager | 1.3.0 | Pairing | ghcr.io/talend/engine-config-manager |
| di-job-deployer | 2.16.0 | Data integration | ghcr.io/talend/di-job-deployer |
| di-job-controller | 2.14.1 | Data integration | ghcr.io/talend/job-controller |
| di-job-restore-orphans | 1.12.0 | Data integration | ghcr.io/talend/di-job-restore-orphans |
| log-collector | 1.2.0 | Common | ghcr.io/talend/dynamic-engine-log-collector |
| data-service-route-deployer | 1.3.0 | Data Services and Routes | ghcr.io/talend/data-service-route-deployer |
| image-builder | 1.1.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.