Automating Dynatrace Image Updates in a Private Registry Without Using latest

arobayo17 — Wed, 20 May 2026 10:38:54 GMT

Hello,
We are currently exploring how to automate version updates for Dynatrace images (Dynatrace Operator, ActiveGate, Code Modules, etc.) in a private registry.
Based on the documentation, an example using skopeo would be:

skopeo copy --all docker://public.ecr.aws/dynatrace/dynatrace-operator:<tag> \ docker://registry.my-company.com/dynatrace-operator:<tag>

However, since our goal is to fully automate this process, we would prefer to use a tag such as latest so that the most recent image can be pulled without having to manually specify the version each time.
That said, according to the documentation:
https://docs.dynatrace.com/docs/shortlink/prepare-private-registry#image-tags

"In all cases, version-based image tagging is employed with container images. Mutable image tags like 'latest' are not used."

Because of this, it is not entirely clear to us what the recommended best practice is for automating image updates in a private registry scenario.
Could you please clarify the correct approach to handle version updates in this case?

topic Automating Dynatrace Image Updates in a Private Registry Without Using latest in Automations

Automating Dynatrace Image Updates in a Private Registry Without Using latest