Default Helm deployment

Helm charts allow you to deploy Dynamic Engine with custom namespaces, service names, and storage configurations.

Tip: About Helm and Kubectl:

They are two options for the deployment of your Dynamic Engine ecosystem. The Helm deployment is recommended.

If you choose Kubectl, skip this section and see Appendix: classic Kubectl deployment.
If you want to change the selected deployment type for your Dynamic Engine and its environment, see Changing the deployment type of a Dynamic Engine.

Dynamic Engine Helm charts are available as images under oci://ghcr.io/talend/helm/ and include:

dynamic-engine-crd: Core custom resource definitions for Dynamic Engine services.
dynamic-engine: Helm chart for a Dynamic Engine instance.
dynamic-engine-environment: Helm chart for Dynamic Engine environments.

Before you begin

A Kubernetes cluster without existing Dynamic Engine services. Dynamic Engine Helm charts will be installed in this cluster.
Privileged access to this Kubernetes cluster.
Installed command-line tools: kubectl and helm. The Helm version must be 3.17.2 or later.

About this task

The following procedure presents the default deployment, which means deploying Dynamic Engine and its environment without customization. Only default Helm values files are used.

Procedure

Use the dynamic-engine-crd Helm chart to install the Dynamic Engine custom resource definitions of a given Helm version.
1. The chart version to use is the same as your Dynamic Engine version. You can find this version using one of the following methods:
  - Run the following Helm command:
    helm show chart oci://ghcr.io/talend/helm/dynamic-engine --version <engine_version>
  - See the version directly from Talend Management Console or check the Dynamic Engine changelog for the chart version included in your Dynamic Engine version.
  - Use an API call to the Dynamic Engine version endpoint.
2. In the Kubernetes cluster, run the following command to install the Helm chart of a given version:
```
helm install dynamic-engine-crd oci://ghcr.io/talend/helm/dynamic-engine-crd --version <helm_chart_version>
```
  Replace <helm_chart_version> with the chart version supported by your Dynamic Engine version.
  Without specifying the version, you install the latest available dynamic-engine-crd chart version.
In the Kubernetes machine, unzip the Helm deployment zip file previously downloaded.
Run this command to deploy the engine instance:
```
helm install dynamic-engine -f $DYNAMIC_ENGINE_ID-helm-values/$DYNAMIC_ENGINE_ID-values.yaml oci://ghcr.io/talend/helm/dynamic-engine
```
This command uses the dynamic-engine Helm charts to deploy the Dynamic Engine instance. Replace $DYNAMIC_ENGINE_ID with the Dynamic Engine ID, for example, c-m-sjufu4qy.

Verify Dynamic Engine status by running this command:

kubectl get de -A

You should see information similar to this:

NAME                               VERSION   STATUS    LAST UPDATE
qlik-dynamic-engine-$DYNAMIC_ENGINE_ID   0.22.0    RUNNING   2m

Run this command to deploy the Dynamic Engine environment.
```
helm install dynamic-engine-env -f $DYNAMIC_ENGINE_ID-helm-values/$DYNAMIC_ENGINE_ENVIRONMENT_ID-values.yaml\
oci://ghcr.io/talend/helm/dynamic-engine-environment
```
This command uses the dynamic-engine-environment Helm chart to deploy the associated Dynamic Engine environment. Replace $DYNAMIC_ENGINE_ENVIRONMENT_ID with the Dynamic Engine environment ID, for example, 67f7d562ffd7c3525a902542.
Verify environment resources.
1. Run the following command:
```
kubectl get dee -A
```
  You should see information reading like this:
```
NAME                                           VERSION   STATUS    LAST UPDATE
qlik-processing-env-$DYNAMIC_ENGINE_ENVIRONMENT_ID   0.22.0    RUNNING   3m
```
2. In Talend Management Console, verify the Dynamic Engine environment status.
  The status should show as Ready.

Results

Once done successfully, the Dynamic Engine environment services are installed in your cluster and connect to the Dynamic Engine.

In Talend Management Console, the status of this environment becomes Ready, confirming that it is ready to run tasks or plans.

If the deployment fails or the Dynamic Engine services are disassociated from the Dynamic Engine, the status become Not ready.

What to do next

Since the Dynamic Engine has been successfully deployed in your Kubernetes, connected to Talend Management Console, and associated with a Dynamic Engine environment, it is ready to run tasks or plans as you usually do on the standard engines. For details about how to add the task to the Dynamic Engine environment for a run, see Adding tasks to a Dynamic Engine environment.

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!

Leave your feedback here