Deleting a Dynamic Engine

You cannot delete a Dynamic Engine with assigned environments.

Before you begin

You must have the Infrastructure Administrator (containing the TMC_CLUSTER_MANAGEMENT permission) role in Talend Management Console.
If the Dynamic Engine has one or more assigned environments, you must unassign them manually from the Dynamic Engine.

Go to the Processing page.
Open the Dynamic Engines tab.
Click the icon next to the Dynamic Engine name from the list.
You can also click the Delete button from the Dynamic Engine details panel.
Confirm the deletion.
If this engine has been deployed in Kubernetes, delete it using the following commands in the Kubernetes terminal:
- If the manifest file for deployment still exists in the cluster, run
```
kubectl delete -f <the-manifest-file>.yaml
```
  Ignore the "qlikruntimeinfra resource not found" error if it occurs.
- If the manifest file does not exist anymore, run these commands sequentially:
  1. kubectl get qlikruntimeinfra
    This gives you the resource name of the Dynamic Engine to be deleted, for example, qlik-dynamic-engine-c-m-e32y3zq1. In this command, qlikruntimeinfra is the predefined source type dedicated to a Dynamic Engine in Kubernetes.
  2. kubectl delete qlikruntimeinfra qlik-dynamic-engine-c-m-e32y3zq1 kubectl delete namespace qlik-dynamic-engine kubectl delete crd qlikruntimeinfra,qlikruntime
    These commands delete the physical entity of the Dynamic Engine, qlik-dynamic-engine-c-m-e32y3zq1, the service namespace qlik-dynamic-engine, and all the custom resource type definitions, that is to say, QlikRuntimeInfra and QlikRuntime.
Once done, run the kubectl get qlikruntimeinfra command again. You should see that no resource is found.

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