Dynatrace Operator release notes version 1.6.1

Latest Dynatrace
Release notes

Release date: July 21, 2025

This page provides an overview of the patches included in Dynatrace Operator version 1.6.1. For detailed information on new features and other enhancements, see the release notes for version 1.6.

Upgrade to 1.6.3

If you're running Dynatrace Operator version 1.6, we recommend upgrading to version 1.6.3 to receive the latest important patches.

Resolved issues

The HostPath of the log monitoring DaemonSet was moved from /tmp/dynatrace to /var/opt/dynatrace to be consistent with the OneAgent.

Secrets generated by the new automatic-tls-certificate feature flag are now properly removed when the ActiveGate configuration is removed from a DynaKube.

Fixed a webhook panic error caused by a missing dynakube.internal.dynatrace.com/instance annotation in the referenced DynaKube.

The validation webhook now checks the .spec.ApiServer value in the EdgeConnect custom resource. Also the respective error message has been improved.

When autoUpdate was disabled and OneAgent version was set, updates by changing the version field were blocked. This issue has been resolved.

Known issues

We have identified the following known issues with Dynatrace Operator version 1.6.0 - 1.6.2.

In Kubernetes environments — especially those utilizing auto-scalers — there are challenges in reliably determining whether a node was intentionally removed or has failed unexpectedly. This ambiguity can lead to a high number of false-positive “Host is unavailable” alerts, impacting monitoring accuracy and alerting quality.

When switching from using the CSI driver without codeModulesImage to using it with node image pull, ensure that the CSI driver’s filesystem does not contain a code module for the specified DynaKube. If it does, the CSI driver will fail and require manual intervention to recover.

Upgrade from Dynatrace Operator version 1.5

No breaking changes.