Choosing an image and registry strategy
Last updated: 10/13/2026
Use this topic to choose how Dynamic Engine
retrieves and uses images for platform deployment and workload execution.
Choose the strategy that matches your goal
| Use case | Recommended topic |
|---|---|
| You want the platform deployment to pull chart and service images through a private registry. | Using a private image registry for Dynamic Engine deployments |
| You need task execution images to be pulled from your custom Docker registry. | Configuring a custom Docker registry for Talend Management Console tasks |
| You want to reduce image footprint and security attack surface by deploying minimal images. | Deploying Dynamic Engine with minimal images |
Scope impact and sequencing
- Deployment registry choices affect platform installation and upgrades.
- Task registry choices affect runtime artifact execution behavior.
- Minimal image adoption should be validated with your existing customization and dependency expectations before broad rollout.
Verify and recover
Validate image pull success and workload startup after each change. If failures occur, revert to the prior known-good image strategy and use troubleshooting guidance in the selected task topic.