Dynatrace Operator release notes version 1.10.2

Latest Dynatrace
Release notes

Release date: July 30, 2026

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

Resolved issues

Fixed a regression in Kubernetes workload and namespace tagging where subsequent matching rules overwrote the previous one. Only the first matching rule for a key is now applied.

For details, see Enrich Kubernetes telemetry with primary Grail fields and tags.

Fixed an issue where the dynatrace-webhook pod entered CrashLoopBackOff when scheduled on a node using the gVisor runtime class (runtimeClassName: gvisor).

Fixed an issue where injected application pods could get stuck at startup because the init container responsible for downloading the OneAgent binary timed out. The download timeout is now set to 15 minutes.

Dynatrace Operator now logs metadata enrichment rules it cannot apply instead of silently ignoring them. This makes it easier to diagnose cases where enrichment rules are not applied

Known issues

Since Dynatrace Operator 1.9.0, a RuntimeDefault seccomp profile is applied to the Dynatrace init container by default. On OpenShift, this can interfere with SecurityContextConstraints (SCCs) — such as anyuid, restricted, or nonroot — that prevent seccomp profile usage, causing the system to fall back to a different SCC (for example restricted-v2). This may render application pods unschedulable or cause workload degradation.
Disable seccomp profile for Dynatrace init containers if you are affected.

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
```

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 operator.apparmor, webhook.apparmor, and csidriver.apparmor Helm values are deprecated. On Kubernetes version 1.31+, set AppArmor using appArmorProfile in the podSecurityContext instead. These values will continue to work until Kubernetes version 1.30 reaches end of life (August 2026). See Enable AppArmor for enhanced security for details.

The “Mark for Termination” event is deprecated and will be removed in a future Operator version. This functionality is now redundant, as it has been superseded by host availability events on host shutdown and reboot introduced in OneAgent version 1.301.

Upgrade from Dynatrace Operator version 1.9

No breaking changes.

Resolved issues

Fixed a regression in Kubernetes workload and namespace tagging where subsequent matching rules overwrote the previous one. Only the first matching rule for a key is now applied.

For details, see Enrich Kubernetes telemetry with primary Grail fields and tags.

Fixed an issue where the dynatrace-webhook pod entered CrashLoopBackOff when scheduled on a node using the gVisor runtime class (runtimeClassName: gvisor).

Fixed an issue where injected application pods could get stuck at startup because the init container responsible for downloading the OneAgent binary timed out. The download timeout is now set to 15 minutes.

Dynatrace Operator now logs metadata enrichment rules it cannot apply instead of silently ignoring them. This makes it easier to diagnose cases where enrichment rules are not applied

Known issues

Since Dynatrace Operator 1.9.0, a RuntimeDefault seccomp profile is applied to the Dynatrace init container by default. On OpenShift, this can interfere with SecurityContextConstraints (SCCs) — such as anyuid, restricted, or nonroot — that prevent seccomp profile usage, causing the system to fall back to a different SCC (for example restricted-v2). This may render application pods unschedulable or cause workload degradation.
Disable seccomp profile for Dynatrace init containers if you are affected.

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
```

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 operator.apparmor, webhook.apparmor, and csidriver.apparmor Helm values are deprecated. On Kubernetes version 1.31+, set AppArmor using appArmorProfile in the podSecurityContext instead. These values will continue to work until Kubernetes version 1.30 reaches end of life (August 2026). See Enable AppArmor for enhanced security for details.

The “Mark for Termination” event is deprecated and will be removed in a future Operator version. This functionality is now redundant, as it has been superseded by host availability events on host shutdown and reboot introduced in OneAgent version 1.301.