Deleting a Dynamic Engine environment

Deleting a Dynamic Engine environment deletes its workspaces, artifacts, tasks, and other properties. This deletion cannot be undone.

You cannot delete an environment assigned to a Dynamic Engine or with the Setup required status.

Before you begin

You must have the Environment Administrator (containing the TMC_ENVIRONMENT_MANAGEMENT permission) role in Talend Management Console.
The Dynamic Engine environment must have the Not assigned or Not ready status.

Procedure

Go to the Environments page.
Open the Dynamic Engine Environments tab.
Click the icon next to the environment name.
You can also click the Delete button from the environment details panel.
Confirm the deletion.
If this environment 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 <environment-manifest-file>.yaml
```
  To locate the correct manifest file to be used, identify the environment ID, which appears in the file name. If the engine is associated with multiple environments, you need this ID to distinguish the correct file.
  Two methods are available to find the environment ID:
  - In Talend Management Console, open the detail page of the environment to be deleted. The ID is visible in the URL. For example, in this URL
    https://app.eu.cloud.talend.com/tmc/environments/dynamic-engine-environments/66f2c0bb3e063d3518122259/overview
    The 66f2c0bb3e063d3518122259 segment is the environment ID.
  - Use the command:
    kubectl get qlikruntime.qlik.com
    This returns the resource name or namespace name with the ID in it. For example, qlik-processing-env-66f2c0bb3e063d3518122259.
- If this manifest file does not exist anymore, run the following commands:
```
kubectl delete qlikruntime <resource-name-of-the-environment>
kubectl delete namespace <namespace-name-of-the-environment>
```
  For example, the resource name or the namespace name to be used can read like: qlik-processing-env-66f2c0bb3e063d3518122259. This name is displayed when you apply the environment manifest file, or you can find it by running kubectl get qlikruntime.qlik.com.
Once done, run the kubectl get qlikruntime.qlik.com command again. You should see that the Dynamic Engine environment resource is not listed anymore.

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