Dynatrace Operator release notes version 1.7.1

Latest Dynatrace
Release notes

Release date: September 20th, 2025

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

Known Issues

We have identified the following known issues with Dynatrace Operator versions 1.7.0–1.7.2. For other known issues, see Dynatrace Operator support and known issues.

Due to optimization of the injected mounts (combining them under /var/lib/dynatrace), Dynatrace components can no longer be injected with the OneAgent.

Classic full-stack and metadata enrichment are not compatible and cannot be used to inject the same application pods.

Resolved issues

Reintroduced the mark for termination event, which was previously removed in Dynatrace Operator version 1.6.0, to address challenges in reliably detecting node terminations in setups facilitating auto-scaler. This feature requires your API token to have the DataExport token scope.

Removal and deprecation notices

The deprecated Dynatrace OneAgent Operator has been removed from the operatorhub.io catalog. Please use our Dynatrace Operator instead.

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 have been removed in Dynatrace Operator version v1.7:
- v1beta1
- v1beta2
The following API versions of the DynaKube CustomResourceDefinition are marked for deprecation and will be removed in the specified Dynatrace Operator versions:
- v1beta3 will be removed with Dynatrace Operator version 1.8

To prevent potential disruptions, we strongly advise keeping your DynaKube API version up to date. Once a version is deprecated and removed, updates may become significantly more complex and time-sensitive.
- More information about the deprecation process of the DynaKube API versions can be found in the migration guide.

The DynaKube field .spec.oneagent.(cloudNativeFullStack|classicFullStack|hostMonitoring).autoUpdate is deprecated and should no longer be used. The flag will be removed in a future version of the Dynatrace Operator. Do one of the following:
- Pin the OneAgent version on your tenant to control all connected Kubernetes clusters at once.
- Use the .spec.oneagent.(cloudNativeFullStack|classicFullStack|hostMonitoring).version field to pin the version on a per-DynaKube basis.

CSI sidecar binaries, located in /usr/local/bin/csi-node-driver-registrar and /usr/local/bin/livenessprobe, are now deprecated and will be removed in a future version of Dynatrace Operator.
Support for OpenShift 4.10 and 4.11 ended in March 2025. As a result, Dynatrace Operator 1.7 will no longer support these versions.

Upgrade from Dynatrace Operator version 1.6

In Dynatrace Operator version 1.7, the DynaKube API versions v1beta1 and v1beta2 are no longer served. Applying DynaKube resources using these versions will fail. Update your DynaKube manifests to v1beta5 before upgrading the Dynatrace Operator. For more information, see Migration guide for DynaKube API versions.