Skip to main content Skip to complementary content

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.

Procedure

  1. Go to the Processing page.
  2. Open the Dynamic Engines tab.
  3. Click the Delete icon next to the Dynamic Engine name from the list.
    You can also click the Delete button from the Dynamic Engine details panel.
  4. Confirm the deletion.
  5. 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 resources.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 qlikruntimeinfras.qlik.com
        This gives you the resource name of the Dynamic Engine to be deleted, for example, qlik-dynamic-engine-c-m-e32y3zq1. In this command, qlikruntimeinfras.qlik.com is the predefined resource definition dedicated to a Dynamic Engine instance in Kubernetes.
      2. kubectl delete qlikruntimeinfra qlik-dynamic-engine-c-m-e32y3zq1
kubectl delete namespace qlik-dynamic-engine
kubectl delete crd qlikruntimeinfras.qlik.com qlikruntimes.qlik.com
        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, qlikruntimeinfras.qlik.com and qlikruntimes.qlik.com.
    Once done, run the kubectl get qlikruntimeinfras.qlik.com command again. You should see that no resource is found.
Troubleshooting:

The entire procedure ensures graceful deletion of a Dynamic Engine instance, including its logical entity in Talend Management Console and its physical entity in Kubernetes. If you keep the logical entity for reuse but delete only the physical entity in Kubernetes, the logical entity turns to the Error status. In addition, if you also delete the deployed Dynamic Engine environment resources in Kubernetes, the logical entity of this environment switches to the Not Ready status.

To reuse the logical entities of the Dynamic Engine instance and its environments, regenerate new manifest files and apply these files to your Kubernetes cluster.

For further information about applying manifest files, see Setting up a Dynamic Engine and a Dynamic Engine environment in Kubernetes.

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