Provisioning a storage class dedicated to Dynamic Engine environment services

Last updated: 10/22/2026

Configure a specific storage class for Dynamic Engine environment services instead of using the default Kubernetes storage class.

Use this topic as the canonical procedure for storage-class deployment settings.

Important: Setting a custom storage class for Dynamic Engine environment services is only allowed during engine deployment.

Dynamic Engine environment services require a storage class that supports ReadWriteMany access mode. For more information about compatible CSI providers, see Supported platforms and storage providers.

For preflight requirements, see Prerequisites to use Dynamic Engine.

Before you begin

Your Dynamic Engine must have been deployed. If not, run this command to deploy it:
```
helm install dynamic-engine -f <engine-id>-helm-values/<engine-id>-values.yaml oci://ghcr.io/talend/helm/dynamic-engine 
```
This is the default deployment, because the current customization is only needed on the Dynamic Engine environment side. For this reason no customization is configured for the Dynamic Engine instance.

Procedure

In the Kubernetes machine, unzip the Helm deployment zip file previously downloaded.
Verify that the storage class to be used exists in your cluster.
```
kubectl get storageclass <storage-class-resource-name>
```
For example, replace <storage-class-resource-name> with the actual resource name to be used, dyn-engine. If this storage class resource does not exist, the following error message is returned:
```
Error from server (NotFound): storageclasses.storage.k8s.io "dyn-engine" not found
```
Contact your Kubernetes administrator to create this storage class resource. It must support the ReadWriteMany access mode.
Create a custom values file specifying the storage class for the Dynamic Engine environment.
```
cat <<EOF > $DYNAMIC_ENGINE_ENVIRONMENT_ID-custom-storageclass-values.yaml
configuration:
  persistence:
    defaultStorageClassName: <storage-class-resource-name>
EOF                               
```
Use the ID of the environment to be deployed for $DYNAMIC_ENGINE_ENVIRONMENT_ID. Use the name of your storage class resource for <storage-class-resource-name>.

Deploy the Dynamic Engine environment chart with your custom storage class configuration.

helm upgrade --install dynamic-engine-environment-$DYNAMIC_ENGINE_ENVIRONMENT_ID \
  -f $DYNAMIC_ENGINE_ENVIRONMENT_ID-values.yaml \
  -f $DYNAMIC_ENGINE_ENVIRONMENT_ID-custom-storageclass-values.yaml \
  oci://ghcr.io/talend/helm/dynamic-engine-environment \
  --version $DYNAMIC_ENGINE_VERSION

Verify that the Dynamic Engine environment is ready and persistent volumes are provisioned.
1. Check the environment status:
```
kubectl get dynamicengineenvs.apps.qlik.com -n <environment-namespace>
```
  The status should show as Running or Ready.
2. Check that persistent volumes have been created for the Dynamic Engine services:
```
kubectl get pvc -n <environment-namespace>
```
  Each service should have a bound persistent volume.

Results

Once done successfully, the Dynamic Engine environment services are installed in your cluster and use the specified storage class. They also connect to the Dynamic Engine.

In Talend Management Console, the status of this environment becomes Ready, confirming that it is ready to run tasks or plans.

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