Dynatrace Operator release notes version 1.6.2

Latest Dynatrace
Release notes

Release date: August 18, 2025

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

Important notice

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

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.
- This issue is fixed in Dynatrace Operator version 1.7+. We highly recommend upgrading to mitigate this issue.
- Other ways to solve the problem:
  - Delete the DynaKube and recreate it. However, this can cause monitoring gaps.
- In case this issue is encountered, reverting back to not using the codeModulesImage will make the CSI driver operational again.
- You can use the find command to check for the downloaded code module for a DynaKube in the filesystem of the CSI server container:
```
  > find /data -name latest-codemodule
  /data/_dynakubes/my-dynakube-1/latest-codemodule
  /data/_dynakubes/my-dynakube-2/latest-codemodule
```

Resolved issues

Resolved an issue where annotations with the prefix metadata.dynatrace.com on scheduled customer application pods were not propagated properly to the enrichment file.

The initContainer in the log monitoring DaemonSet now respects resource values set in .spec.templates.logMonitoring.resources in the DynaKube.

To promote consistent configurations and avoid the anti-pattern of using the latest tag, it will be required to explicitly specify an OpenTelemetry collector image in the .spec.templates.otelCollector.imageRef field in future operator releases. To prepare for this update, users leveraging the Telemetry ingest feature will now receive a warning if an OpenTelemetry collector image is not defined in the configuration.

Removal and deprecation notices

The Helm repository located in dynatrace/helm-charts is deprecated and will stop receiving updates in a future release! If you are still using it, please update the URL to dynatrace/dynatrace-operator or switch to the OCI registry-based approach. Update the Helm repository URL with the following commands:
```
helm repo remove dynatrace
helm repo add dynatrace https://raw.githubusercontent.com/Dynatrace/dynatrace-operator/main/config/helm/repos/stable
```

The following API versions of the DynaKube CustomResourceDefinition are marked for deprecation and will be removed in specified Dynatrace Operator versions:
- v1beta1 will be removed with Dynatrace Operator version 1.7
- v1beta2 will be removed with Dynatrace Operator version 1.7
- v1beta3 will be removed with Dynatrace Operator version 1.8

Upgrade from Dynatrace Operator version 1.5

There are no breaking changes in this version.