Talend Dynamic Engine

This release note covers the release of Dynamic Engine v1.0.0 and its subsequent maintenance releases.

New features

Feature	Description
Dynamic Engine v1.0.0	Dynamic Engine v1.0.0 delivers major improvements in performance, security, deployments, and platform support. Highlights include: The general availability of air-gapped deployment support. For a configuration example, see Using an HTTP proxy for Dynamic Engine services in air-gapped environments. GKE (Google Kubernetes Engine) is now a supported Kubernetes runtime. For an example of deploying Dynamic Engine in GKE, see Deploying Dynamic Engine in a GKE cluster Support for custom keystores and truststores is extended to Data Services and Routes. For the full changelog and further improvements, see the Dynamic Engine v1.0.0 changelog. For deployment and configuration guidance, see Dynamic Engine Configuration Guide.

Feature

Description

Dynamic Engine v1.0.0

Dynamic Engine v1.0.0 delivers major improvements in performance, security, deployments, and platform support. Highlights include:

The general availability of air-gapped deployment support. For a configuration example, see Using an HTTP proxy for Dynamic Engine services in air-gapped environments.
GKE (Google Kubernetes Engine) is now a supported Kubernetes runtime. For an example of deploying Dynamic Engine in GKE, see Deploying Dynamic Engine in a GKE cluster
Support for custom keystores and truststores is extended to Data Services and Routes.

For the full changelog and further improvements, see the Dynamic Engine v1.0.0 changelog.

For deployment and configuration guidance, see Dynamic Engine Configuration Guide.

Release	Description
Dynamic Engine v1.0.1 changelog	This maintenance release adapts the CPU limit of the engine operator to runc 1.3.2.
Dynamic Engine v1.0.2 changelog	This maintenance release ensures an error is raised if the name of the Kubernetes secret that stores your registry credentials is not set.

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!