Skip to main content Skip to complementary content

Dynamic Engine v1.1.0 release

Dynamic Engine v1.1.0 adds multi-architecture support for Linux x86-64 (linux/amd64) and Linux ARM64 (linux/arm64), enables nodeSelector and affinity rules in Helm charts, and includes many critical dependencies updates for security, flexibility, and performance.

Release information

  • Release Name: Dynamic Engine 1.1.0 (2025-12)
  • Release Date: December 11, 2025
  • Compatibility: Kubernetes v1.30 and above

Notable new features

  • DPE-1147: Support for Linux ARM64 nodes in Dynamic Engine Kubernetes clusters:
    • All Dynamic Engine images are now available for both Linux x86-64 (linux/amd64) and Linux ARM64 (linux/arm64) architectures.
    • The nodeSelector and affinity rules are now supported in Dynamic Engine Helm charts.

Key improvements and security enhancements

  • DPE-2976: All images upgraded from Rocky Linux 9.6 to Rocky Linux 10.1, addressing CVEs in 9.6 for improved security and platform stability.
  • DPE-1975: data-service-route-deployer now supports rolling update strategy, enabling zero-downtime service version upgrades.
  • DPE-2076: Removed register-oidc to streamline deployment configuration.
  • DPE-2078: Image registry credentials are now hidden in the services installation process, improving security and preventing accidental credential exposure.
  • DPE-1972: Helm history for installed Dynamic Engine services reduced to 3 entries, decreasing memory footprint.
  • DPE-2081: Removed qlikruntime (v1) custom resource definitions.

Included services

Installer charts
Helm chart name Chart version Scope Artifact path
dynamic-engine-crd 1.1.0 Custom resource definitions ghcr.io/talend/helm/dynamic-engine-crd
dynamic-engine 1.1.0 Dynamic Engine infrastructure ghcr.io/talend/helm/dynamic-engine
dynamic-engine-environment 1.1.0 Dynamic Engine environment ghcr.io/talend/helm/dynamic-engine-environment
Services charts
Service Chart version Artifact path
reloader 2.2.5 ghcr.io/talend/helm/reloader
docker-registry 3.0.0 ghcr.io/talend/helm/docker-registry
engine-config-manager 2.7.0 ghcr.io/talend/helm/dpe-engine-config-manager
di-job-deployer 1.22.0 ghcr.io/talend/helm/dpe-di-job-deployer
di-job-controller 1.12.0 ghcr.io/talend/helm/dpe-job-controller
log-collector 1.5.0 ghcr.io/talend/helm/dpe-log-collector
data-service-route-deployer 1.4.0 ghcr.io/talend/helm/dpe-data-service-route-deployer
Services images
Service Image version Feature Artifact path
engine-operator 1.1.0 Infrastructure ghcr.io/talend/engine-operator
reloader v1.4.10 Infrastructure ghcr.io/talend/reloader
docker-registry 3.0.0 Infrastructure ghcr.io/talend/registry
kube-base 5.0.0 Infrastructure ghcr.io/talend/kube-base
engine-config-manager 1.8.0 Pairing ghcr.io/talend/engine-config-manager
di-job-deployer 2.22.0 Data integration ghcr.io/talend/di-job-deployer
di-job-controller 2.20.0 Data integration ghcr.io/talend/job-controller
di-job-restore-orphans 1.17.0 Data integration ghcr.io/talend/di-job-restore-orphans
di-job-runner-jre17 2.20.0 Data integration ghcr.io/talend/di-job-runner-jre17
log-collector 1.7.0 Common ghcr.io/talend/dynamic-engine-log-collector
fluent-bit 4.0.13 Common ghcr.io/talend/fluent-bit
data-service-route-deployer 1.9.0 Data Services and Routes ghcr.io/talend/data-service-route-deployer
image-builder 1.7.0 Data Services and Routes ghcr.io/talend/image-builder
jre17-base-minimal 5.0.0 Data Services and Routes ghcr.io/talend/jre17-base-minimal

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.

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!