Dynatrace Operator release notes version 1.10.3

Latest Dynatrace
Release notes

Release date: October 15, 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.3. For detailed information on new features and other enhancements, see the release notes for version 1.10.0.

Resolved issues

Fixed an issue where the CSI driver cleanup could delete OneAgent code module binaries still in use by running pods. Without this fix, a container restart (for example, after an out-of-memory termination) could leave the application without its OneAgent files, so the application would no longer be monitored.

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

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 additional migration steps are required beyond those described in the upgrade notes for version 1.10.0.