Dynatrace Operator release notes version 1.7.2

Latest Dynatrace
Release notes

Release date: November 12th, 2025

Resolved issues

The OpenTelemetry Collector used for telemetry ingest now automatically includes the local ActiveGate service URL in its no-proxy configuration, ensuring that connections to the local ActiveGate bypass any configured proxies and avoiding unnecessary proxy hops or related connection issues.

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 1.7.0:
- 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.0 will no longer support these versions.

Upgrade from Dynatrace Operator version 1.6

Starting with this version, it is no longer possible to deploy a DynaKube with API versions v1beta1 or v1beta2. Please update your DynaKube to the latest API version, v1beta5, before upgrading your Dynatrace Operator installation. For more information, see Migration guides for DynaKube apiVersions.