Skip to main content Skip to complementary content

Dynamic Engine v1.3.0 release

Dynamic Engine v1.3.0 embeds service charts in Dynamic Engine charts, provides a profile to switch service images, reduces image size, and includes critical security and stability improvements.

Release information

  • Release Name: Dynamic Engine 1.3.0 (2026-02)
  • Release Date: February 18, 2026
  • Compatibility: Kubernetes v1.30 and above

Migration information

If you are upgrading from a version earlier than 1.3.0, run specific preparation and cleanup commands before the upgrade. These commands vary depending on whether you use Helm-based or manifest-based upgrades:

  • For Helm-based upgrades (using helm upgrade): Follow the commands provided in the readme.txt file included in the generated deployment zip. For an example of this preparation plus the upgrade to 1.3.0, see Special procedure to upgrade Dynamic Engine to 1.3.0.
  • For manifest-based upgrades (using kubectl apply): Use the commands below:
    1. Remove the old Helm release annotations:
      • For Dynamic Engine, run:
        kubectl annotate svc,secret,cm,pvc,deploy,cronjob,role,rolebinding,hpa,PodDisruptionBudget,NetworkPolicy,sa \
          -n qlik-dynamic-engine \
          -l 'app in (reloader)' \
          meta.helm.sh/release-name- meta.helm.sh/release-namespace-
      • For each Dynamic Engine environment, run:
        kubectl annotate svc,secret,cm,pvc,deploy,cronjob,role,rolebinding,hpa,PodDisruptionBudget,NetworkPolicy,sa,clusterrole,clusterrolebinding \
          -n qlik-processing-env-$DYNAMIC_ENGINE_ENVIRONMENT_ID \
          -l 'app.qlik.com/processing-environment-id=$DYNAMIC_ENGINE_ENVIRONMENT_ID' \
          meta.helm.sh/release-name- meta.helm.sh/release-namespace-
        Replace $DYNAMIC_ENGINE_ENVIRONMENT_ID with the actual value.
    2. Remove some old Helm secrets from the Dynamic Engine deployment and its environments.
      • For Dynamic Engine, run:
        kubectl delete secret -A -l owner=helm,name=reloader
      • For each Dynamic Engine environment, run:
        kubectl delete secret -A -l owner=helm,'name in (di-job-controller-$DYNAMIC_ENGINE_ENVIRONMENT_ID, \
          di-job-deployer-$DYNAMIC_ENGINE_ENVIRONMENT_ID, engine-config-manager-$DYNAMIC_ENGINE_ENVIRONMENT_ID, \
          log-collector-$DYNAMIC_ENGINE_ENVIRONMENT_ID)'
        Each placeholder $DYNAMIC_ENGINE_ENVIRONMENT_ID needs to be replaced by the corresponding environment ID.
    Information noteTip: The following warning messages are displayed for information only. They do not prevent the upgrade from being completed successfully.
    Warning: resource serviceaccounts/dpe-di-job-restore-orphans-sa is missing ...
    Warning: resource serviceaccounts/dpe-di-job-deployer-sa is missing...
    Warning: resource serviceaccounts/engine-config-manager-sa is missing...
    Warning: resource serviceaccounts/job-controller-sa is missing... \
    <!-- Some lines are skipped for brevity -->

Deprecation information

The support for the generation of manifests has been extended. The corresponding endpoint has been deprecated and will be removed in future versions to only support the generation of Helm values.

Notable new features

  • DPE-2359: Service charts have been embedded in Dynamic Engine charts.

Key improvements and fixes

  • DPE-2582: Reduced image size
  • Security upgrade: Updated JRE 21 and JRE 17 with critical security patches for improved stability and security.

Included services

Installer charts
Helm chart name Chart version Scope Artifact path
dynamic-engine-crd 1.3.0 Custom resource definitions ghcr.io/talend/helm/dynamic-engine-crd
dynamic-engine 1.3.0 Dynamic Engine Infrastructure ghcr.io/talend/helm/dynamic-engine
dynamic-engine-environment 1.3.0 Dynamic Engine environment ghcr.io/talend/helm/dynamic-engine-environment
Service charts
Service Chart version Artifact path
reloader 2.2.7 ghcr.io/talend/helm/reloader
docker-registry 3.0.0 ghcr.io/talend/helm/docker-registry
engine-config-manager 2.9.3 ghcr.io/talend/helm/dpe-engine-config-manager
di-job-deployer 1.27.3 ghcr.io/talend/helm/dpe-di-job-deployer
di-job-controller 1.15.6 ghcr.io/talend/helm/dpe-job-controller
log-collector 1.8.1 ghcr.io/talend/helm/dpe-log-collector
data-service-route-deployer 1.8.1 ghcr.io/talend/helm/dpe-data-service-route-deployer
Service images
Service Image version Feature Artifact path
engine-operator 1.4.0 Infrastructure ghcr.io/talend/engine-operator
reloader v1.4.12 Infrastructure ghcr.io/talend/reloader
docker-registry 3.0.0 Infrastructure ghcr.io/talend/registry
engine-config-manager 1.12.0 Pairing ghcr.io/talend/engine-config-manager
di-job-deployer 2.25.0 Data integration ghcr.io/talend/di-job-deployer
di-job-controller 2.23.0 Data integration ghcr.io/talend/job-controller
di-job-restore-orphans 1.20.0 Data integration ghcr.io/talend/di-job-restore-orphans
log-collector 1.10.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.12.1 Data Services and Routes ghcr.io/talend/data-service-route-deployer
image-builder 1.10.0 Data Services and Routes ghcr.io/talend/image-builder

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!