Dynatrace Operator manages the rollout and updates of the following components in Kubernetes:
The default settings for OneAgent and ActiveGate automatically roll out updates as soon as they become available. DynaKube also defaults to update all pods when updates are detected automatically. Note that updates may take up to 15 minutes due to Dynatrace Operator checking for updates at 15-minute intervals. If you set a custom image, it will disable automatic updates.
Set the target version on the Dynatrace Server to a relative version, for example, Latest stable version. Dynatrace Operator will periodically check for updates and propagate them to the Kubernetes environment. An update of the OneAgent version will always cause restart of the OneAgent pods.
Minimal DynaKube configuration that uses auto-update:
apiVersion: dynatrace.com/v1beta5kind: DynaKubemetadata:name: dynakubenamespace: dynatracespec:apiUrl: https://ENVIRONMENTID.live.dynatrace.com/apioneAgent:cloudNativeFullStack: {}
Update windows currently do not apply in Kubernetes environments.
To disable auto-update, set the image field in the DynaKube. Omit the field to keep auto-update enabled.
# Auto-update enabled (default) — omit imagespec:oneAgent:cloudNativeFullStack: {}# Auto-update disabled — pin a specific imagespec:oneAgent:cloudNativeFullStack:image: public.ecr.aws/dynatrace/dynatrace-oneagent:<tag>
While new images are downloaded, applications are only updated when restarted. Keep in mind that autoscaling also injects the most recent CodeModule.
Similar to OneAgent, the ActiveGate update can be configured in the UI, resulting in a changed ActiveGate image, visible to Dynatrace Operator.