Skip to main content Skip to complementary content

Upgrading Dynamic Engine version

Upgrade your Dynamic Engines to the latest version.

Before you begin

  • You must have the Infrastructure Administrator role (TMC_CLUSTER_MANAGEMENT) to upgrade the Dynamic Engine version.

Procedure

  1. Go to the Processing page.
  2. Open the Dynamic Engines tab.
    You can see a blue dot on the Dynamic Engine names when a new version is available.
    New version available for a Dynamic Engine.
  3. Hover over the Dynamic Engine name then click Open menu > Update.
    You can also click the Dynamic Engine name to open its details panel then click the Deploy tab.
    You can also click the Deploy Dynamic Engine button from the Dynamic Engine details page.
  4. Select the type of deployment and its latest version from the list.
    By default, the latest version of the Helm is selected.

    Example

    The upgrade dialog
  5. Click Download to download the deployment files in a zip.
  6. Unzip the file previously downloaded.
    Information noteImportant: Do not change the content of this manifest file. Only the default configuration pre-defined in this file is supported.
  7. In your Kubernetes terminal, run the following commands in the order presented here to set up the Dynamic Engine instance:
    • For Helm:
      1. helm upgrade dynamic-engine-crd oci://ghcr.io/talend/helm/dynamic-engine-crd --version \
        ${DYN_ENG_VERSION}
      2. helm upgrade dynamic-engine-<engine-id> oci://ghcr.io/talend/helm/dynamic-engine --version \
        ${DYN_ENG_VERSION} -f <engine-id>-values.yaml
      3. helm upgrade dynamic-engine-environment-<environment-id> oci://ghcr.io/talend/helm/dynamic-engine-environment \
        --version ${DYN_ENG_VERSION} -f <environment-id>-values.yaml
      For further information about the three charts in these commands, see (Recommended) Helm deployment.
    • For Kubectl:
      1. kubectl apply -f custom-resource-definitions.yaml
      2. kubectl apply -f resources.yaml
      3. Execute the following command to set up the environments.
        kubectl apply -f resources-<environment_id>.yaml
    Only one environment has been created and assigned in this example. If a Dynamic Engine instance is associated with multiple environments, you need the environment IDs to identify the correct files.

Results

The Dynamic Engine version is upgraded.

You can see the deployed version from the Deploy tab of the Dynamic Engine details panel.

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!