Dynatrace Pod Redeployments After Image Updates Within Private Registry

Summary

There are times when you may wish to use a private registry for OneAgent and ActiveGate image storage to ensure consistency and version rollouts.

Problem

If you use the “latest” tag for every new OneAgent / ActiveGate image pushed to the registry, then the Dynatrace Operator will not recognize that there is a “new latest” depending on your setting of the OneAgent / ActiveGate image value within your dynakube CRD creation yaml.

Resolution

Once the new “latest” image is in your registry, you can manually trigger a redeployment of the Dynatrace OneAgent and ActiveGate pods to roll out the newest image versions through the kubectl rollout command.

kubectl get all -n dynatrace<br>kubectl rollout restart daemonset/<dynakube name>-oneagent -n dynatrace <br>kubectl rollout restart statefulset/<ACTIVEGATE-STATEFULSET-NAME> -n dynatrace 

What’s next

If you don’t see the expected re-deployments for the OneAgent or ActiveGate pods after using the above steps, please open a support ticket, mention that this article was used, and provide the following in the ticket:

  • a link to this article
  • a Dynatrace Operator Support archive
  • OR a copy of your dynakube CRD creation yaml file