Skip to main content Skip to complementary content

Deleting a Dynamic Engine

Before you begin

  • You must have the Infrastructure Administrator role with the TMC_CLUSTER_MANAGEMENT permission in Talend Management Console.
  • You cannot delete an engine with assigned environments. Unassign all environments first. For more information, see Unassigning an environment from a 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 to delete.
    You can also click the Delete button from the Dynamic Engine details panel.
  4. Confirm deletion.
  5. If any unassigned environments have been deployed in Kubernetes, delete their resources:
    1. In the Kubernetes terminal, run kubectl get qlikruntime.qlik.com to list environment resources.
    2. Delete each resource namespace:
    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.
    Once done, run the kubectl get qlikruntime.qlik.com command again. You should see that the Dynamic Engine environment resource is not listed anymore.
  6. If the engine has been deployed in Kubernetes, delete it using the following commands in the Kubernetes terminal: 
    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, 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. You should see that no resource is found.

Results

This procedure gracefully deletes the engine's logical entity in Talend Management Console and physical deployment (the engine's physical entity and related environment resources) in Kubernetes.

This procedure deletes only the Kubernetes deployments of the unassigned Dynamic Engine environments but does not delete their logical entities in Talend Management Console.
  • To delete those logical entities of the environments, see Deleting a Dynamic Engine environment.
  • To reuse those logical entities, assign them to a new Dynamic Engine, generate new manifest files, and apply these files to your Kubernetes cluster.
Troubleshooting:
Partial deletion of a Dynamic Engine can cause issues:
  1. Deleting only the Kubernetes deployment (physical entity) causes the engine's logical entity to show the Error status.
  2. Deleting deployed environment resources sets the status of these environments to Not Ready in Talend Management Console.
To fix and reuse these logical entities,
  1. Assign environments to a new Dynamic Engine.
  2. Generate new manifest files for these entities.
  3. 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