# Upgrading Dynamic Engine version

Upgrade your Dynamic Engines to the latest version.

When upgrading from 1.6.x to 1.7.0, use the [1.7.0 migration procedure](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/dynamic-engine-migration-to-1-7 "Use this procedure when upgrading from 1.6.x to 1.7.0 with persistence still enabled in 1.6.x.") if persistence is enabled. If you already disabled persistence in 1.6.x, continue with this generic upgrade procedure.

Version 1.7.0 supports Helm deployment only. Existing manifest-based deployments cannot be migrated to Helm. Do not use the Kubectl option in this procedure for version 1.7.0.

Information noteTip:

Dynamic Engine 1.3.0 changes how Helm manages service charts. These changes require resource reassignment and metadata cleanup if you are upgrading from version 1.2.x or earlier to any 1.3.x version. For preparation and upgrade instructions, see [Special procedure to upgrade Dynamic Engine to 1.3.x](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/dynamic-engine-migration-to-1-3 "Dynamic Engine 1.3.0 changes how services are installed. To upgrade your engine to this version, you must prepare your cluster for upgrade by cleaning up or reassigning existing resources, regardless of whether you deployed using Helm or Kubectl manifest files (both valid deployment methods prior to v1.7.0).").

## 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.](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Resources/images/dynamic-engine-update-available.png)
3. Right-click the Dynamic Engine name then click Update.

   You can also click the Dynamic Engine name to open its details panel then click the Deploy tab.
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](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Resources/images/dynamic-engine-upgrade-dialog.png)
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 Helm values 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:

   Information noteImportant: If your engine was deployed before v1.7.0 using the Kubectl method, it cannot be upgraded. There is no migration path from Kubernetes manifests to Helm charts. The only way forward is a full redeployment using Helm deployment files. For details, see [Classic Kubectl deployment](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/deploy-with-standard-manifest-files "Reference information for the classic Kubectl deployment method, available only for engines and environments deployed before v1.7.0. Unlike Helm, Kubectl does not allow custom deployment configuration.").
   1. ```
      helm upgrade dynamic-engine-crd oci://ghcr.io/talend/helm/dynamic-engine-crd --version \
      ${DYN_ENG_VERSION}
      ```
   2. ```
      helm upgrade dynamic-engine-$DYNAMIC_ENGINE_ID oci://ghcr.io/talend/helm/dynamic-engine --version \
      ${DYN_ENG_VERSION} -f $DYNAMIC_ENGINE_ID-values.yaml --force-conflicts
      ```
   3. ```
      helm upgrade dynamic-engine-environment-$DYNAMIC_ENGINE_ENVIRONMENT_ID oci://ghcr.io/talend/helm/dynamic-engine-environment \
      --version ${DYN_ENG_VERSION} -f $DYNAMIC_ENGINE_ENVIRONMENT_ID-values.yaml --force-conflicts
      ```

   For further information about the three charts in these commands, see [Default Helm deployment](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/deploy-with-helm-values-files "Helm charts allow you to deploy Dynamic Engine with custom namespaces, service names, and storage configurations.").

   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.