# Known limitations of Dynamic Engine

The Dynamic Engine solution still has the following known limitations:

* Each Kubernetes cluster can only have one Dynamic Engine by design. A Dynamic Engine provides the core infrastructure services for task and plan executions.
* There is no mechanism to prevent deploying more than one Dynamic Engine in a Kubernetes cluster. Doing this may cause unexpected connectivity and performance issues for Talend Management Console, Dynamic Engines, and Dynamic Engine environments.
* The Kubernetes cluster in which Dynamic Engine is deployed must have access to public internet.
* The following task execution features for data integration Jobs are not supported:
  * Remote debugging of a Data Integration Job on Dynamic Engines
  * User impersonation
  * Invoking non-Linux commands with the tSystem component is not supported

## Local storage and persistent data in Dynamic Engine environments

Local file system components (such as tFileInputDelimited and tFileOutputDelimited) require persistent storage for data to survive across Job executions and be shared between Jobs. However, Kubernetes containers are ephemeral by default, and data is destroyed after task completion. You have two approaches to address this:

1. Mount Kubernetes resources:

   You can mount Kubernetes resources in your task containers and configure local file components to read from or write to the mounted path. This provides persistent storage in your Dynamic Engine environment without relying on external cloud services.

   For details, see [Mounting custom Kubernetes resources in Dynamic Engine environments](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/custom-kubernetes-resource-mounting "Customizing Dynamic Engine environments through Kubernetes resource mounting: ConfigMap for non-sensitive configuration, Secret for credentials, volumes for files and certificates, PersistentVolumeClaim for persistent storage, and securityContext for user permissions.").

2. Use cloud storage components (S3, Azure, or equivalent):

   Cloud storage components (S3, Azure Data Lake Storage, Azure Blob, etc.) connect Dynamic Engine to external storage solutions, providing persistent data handling beyond the cluster.

   For further information about how to use cloud storage components in your Jobs, see:

   * [Amazon S3 components](https://help.qlik.com/talend/en-US/components/8.0/amazon-s3/amazon-s3-component)
   * [Azure Data Lake Storage Gen2](https://help.qlik.com/talend/en-US/components/8.0/azure-data-lake-storage-gen2)
   * [Azure Storage Blob](https://help.qlik.com/talend/en-US/components/8.0/azure-storage-blob)
   * [Azure Storage Queue](https://help.qlik.com/talend/en-US/components/8.0/azure-storage-queue)
   * [Azure Storage Table](https://help.qlik.com/talend/en-US/components/8.0/azure-storage-table)

Information noteTip: While Talend Studio offers native support for S3 and Azure, you have the flexibility to use either approach, or both together, depending on your data persistence and integration requirements.