Dynatrace Operator release notes version 1.10.1

Latest Dynatrace
Release notes

Release date: July 22, 2026

Minimum operator version required for direct upgrade: 1.5.0—see Upgrade from older versions. Review the release notes for each intermediate version and pay attention to breaking changes before upgrading.

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

Resolved issues

Fixed TLS certificate verification errors that prevented applications instrumented via classicFullstack from sending data through the in-cluster ActiveGate. TLS certificate verification is enabled by default and can be disabled via the feature.dynatrace.com/automatic-tls-certificate feature flag.

Fixed an issue where auto-update for ActiveGate, CodeModule, and OneAgent did not receive automatic image updates.

Fixed an issue where a newly introduced rollout integrity check caused OneAgent deployments to stall indefinitely.

Fixed an issue where OneAgent endpoints were not correctly translated into Istio ServiceEntries and VirtualServices when spec.enableIstio was enabled.

Known issues

Resolved with Dynatrace Operator version 1.10.3 When a OneAgent code modules version is updated, the CSI driver's cleanup of old code modules versions could delete OneAgent binaries that running pods still depend on. Pods created after the update are not affected, but if a container in an already running pod restarts (for example, after an out-of-memory termination), the application loses its OneAgent files, which leads to the application no longer being monitored. Until you upgrade, pin codeModulesImage to a specific version to avoid triggering the cleanup.

Removal and deprecation notices

The Helm repository located in dynatrace/helm-charts is archived and no longer receives updates. If you still install or upgrade Dynatrace Operator from it, switch to the OCI registry:
```
helm upgrade dynatrace-operator oci://public.ecr.aws/dynatrace/dynatrace-operator \
  --version <version> \
  --namespace dynatrace \
  --reset-then-reuse-values \
  --install
```
If you can't use OCI, point your Helm repository to dynatrace/dynatrace-operator instead:
```
helm repo remove dynatrace
helm repo add dynatrace https://raw.githubusercontent.com/Dynatrace/dynatrace-operator/main/config/helm/repos/stable
```
For details, see Migrate from the legacy Helm repository.

Removed DynaKube API version v1beta3; v1beta4 is now deprecated: The v1beta3 version has been removed from the DynaKube CRD. The v1beta4 version is now deprecated. Migrate your DynaKube resources to v1beta6. For details, see DynaKube API version migration.

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

Upgrade to version 1.10.1 to receive all fixes listed on this page. No additional migration steps are required beyond those described in the upgrade notes for version 1.10.0.