Dynatrace Operator support and known issues

  • 5-min read

Dynatrace offers support for Kubernetes shortly after a new Kubernetes or OpenShift release. Once the new Kubernetes/OpenShift release candidate versions are available, Dynatrace tests these versions, including the latest OneAgent, ActiveGate, and Dynatrace Operator versions.

The table below lists the verified and tested release versions:

Kubernetes upstream versionOpenShift versionMinimum OneAgent versionMinimum ActiveGate versionMinimum Dynatrace Operator versionRecommended Dynatrace Operator versionEnd of support (Kubernetes)End of support (OpenShift)
1.341.3191.319v1.6.xv1.7.0+Nov 1, 2027
1.334.201.3191.319v1.1.xv1.7.0+Jul 1, 2027Mar 1, 2028
1.324.191.3091.309v1.1.xv1.7.0+Mar 1, 2027Mar 1, 2028
1.314.181.2971.297v1.1.xv1.7.0+Jan 1, 2027Aug 1, 2028
1.304.171.2911.291v1.1.xv1.7.0+Aug 1, 2026Jul 1, 2027
1.294.161.2811.281v0.14.xv1.7.0+Mar 1, 2026Sep 1, 2027
1.284.151.2751.275v0.12.xv1.7.0+Nov 1, 2025Nov 1, 2026
1.274.141.2691.269v0.10.xv1.7.0+Jul 1, 2025Nov 1, 2026
1.264.131.2591.257v0.10.xv1.7.0+Mar 1, 2025Feb 1, 2026
1.254.121.2491.251v0.8.xv1.4.2+Nov 1, 2024Feb 1, 2026
1.244.111.2411.243v0.7.xv1.3.2+Aug 1, 2024Mar 1, 2025
1.234.101.2331.233v0.4.xv1.0.12Apr 1, 2024Mar 1, 2025
1.224.91.2271.223v0.3.xv1.0.12Jan 1, 2024May 1, 2024
1.214.81.2171.215v0.3.xv0.12.11Nov 1, 2023May 1, 2024
1.204.71.2071.211v0.3.xv0.6.0Aug 1, 2023Aug 1, 2023
1.194.61.1991.205v0.3.xv0.6.0Aug 1, 2023Aug 1, 2023
3.11v0.2.2v0.2.2Aug 1, 2023Aug 1, 2023
1

A new Go version used in Dynatrace Operator is incompatible with the CRI-O version of OpenShift 4.8 and Kubernetes 1.21. See the required manual workaround in Dynatrace Operator release notes version 0.13.0.

2

Dynatrace Operator version 1.0.1 is recommended for Kubernetes 1.22 and 1.23. Upgrading to version 1.1.0+ is suggested for OpenShift 4.8 and above.

Full support is provided until a Kubernetes or OpenShift version reaches end of life. After that, Dynatrace provides maintenance support for approximately one year. End-of-support dates are announced in End-of-support announcements.

The main distinction between full support and maintenance support is that Dynatrace reduces the daily testing activities during the maintenance support period.

During the full support and maintenance support periods, each encountered bug undergoes a backport assessment. Depending on the severity and change risk, the fix is either backported and released with a patch version or fixed in the next version. For details, refer to the relevant Dynatrace release notes.

Dynatrace Operator support

The Dynatrace Operator is available on the following architectures:

  • x86
  • ARM
  • ppc64le
  • s390x 1

In cases where issues related to the Dynatrace Operator cannot be replicated by Dynatrace on x86 or ARM architectures and are identified as specific to ppc64le, you need to reach out to dt-operator@ibm.com for further support. Additional information can be found in the associated open-source pull request for the Dynatrace Operator on GitHub.

Dynatrace Operator is responsible for rollout and lifecycle management of various Dynatrace components in Kubernetes and OpenShift (including ActiveGate and OneAgent). Dynatrace Operator is an open-source project maintained on GitHub. It follows the major.minor.patch semantic versioning schema, with a release cadence of minor versions being released roughly every 2–3 months.

The three latest Dynatrace Operator versions are tested with the latest Kubernetes and OpenShift versions. Additionally, we perform a backport assessment for any bug or vulnerability to analyze the severity and change risk of the fix. We recommend that you use the latest patch version, as the newly implemented features increment the minor version. For details, see the Dynatrace Operator release notes.

All Dynatrace Operator versions that are not considered end-of-life are treated as being in maintenance mode, which includes our regular customer support processes. Versions in maintenance mode do not receive bug fixes and vulnerability backports. See end-of-support announcements on End-of-support announcements.

Known issues and resolutions

A list of known issues for Dynatrace Operator versions and how they affect various components. These issues are present in released versions of the Dynatrace Operator and may require a minor version upgrade to resolve them!

Dynatrace component injection

Dynatrace Operator version 1.7.0 Dynatrace Operator version 1.7.1 Dynatrace Operator version 1.7.2

Issue

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

  • Dynatrace components contain configuration in /var/lib/dynatrace that is hidden by mounts added by the Webhook injection.

By default, monitoring for the Dynatrace Operator namespace (and therefore Dynatrace components) is not enabled. The issue can surface if the feature.dynatrace.com/ignored-namespaces feature flag is used to override ignored namespaces to include the Dynatrace Operator namespace.

Resolution

Configure the dynatrace.com/split-mounts pod annotation (requires Dynatrace Operator version 1.8.0+) on affected pods.

Classic full-stack with metadata enrichment

Dynatrace Operator version 1.7.0 Dynatrace Operator version 1.7.1 Dynatrace Operator version 1.7.2

Issue

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

Both OneAgent and Webhook injection attempt to add a mount to the /var/lib/dynatrace directory in the application pod. These mounts are incompatible and cannot coexist.

Resolution

If using Dynatrace Operator versions below 1.7.0:

  • With OneAgent version 1.333, no changes are required.
  • With OneAgent version 1.331 or earlier, the remountOperatorEnrichment debug flag needs to be configured for the OneAgent.

Upgrade to Dynatrace Operator version 1.8.0 (when available).

Host availability detection

Dynatrace Operator version 1.6.0 Dynatrace Operator version 1.6.1 Dynatrace Operator version 1.6.2 Dynatrace Operator version 1.7.0 Dynatrace Operator version 1.7.1

Issue

  • In Kubernetes environments — especially those utilizing auto-scalers — there are challenges in reliably determining whether a node was intentionally removed or has failed unexpectedly. This ambiguity can lead to a high number of false-positive “Host is unavailable” alerts, impacting monitoring accuracy and alerting quality.

Resolution

Upgrade to Dynatrace Operator version 1.7.2+ or 1.6.3.

Switch to Node image pull with Code modules image

Dynatrace Operator version 1.5.0 Dynatrace Operator version 1.5.1 Dynatrace Operator version 1.6.0 Dynatrace Operator version 1.6.1 Dynatrace Operator version 1.6.2

Issue

When switching from using the CSI driver without codeModulesImage to using it with node image pull, ensure that the CSI driver’s filesystem does not contain a code module for the specified DynaKube. If it does, the CSI driver will fail and require manual intervention to recover.

  • If this issue is encountered, reverting back to not using the codeModulesImage will make the CSI driver operational again.

  • You can use the find command to check for the downloaded code module for a DynaKube in the filesystem of the CSI server container:

    > find /data -name latest-codemodule
    /data/_dynakubes/my-dynakube-1/latest-codemodule
    /data/_dynakubes/my-dynakube-2/latest-codemodule

Resolution

  • Upgrade to Dynatrace Operator version 1.7.0+.

Other ways to solve the problem:

  • Delete the DynaKube and recreate it. This will cause monitoring gaps.

Incompatibilities with specific component versions

Dynatrace Operator version 1.5.0+

The automatic TLS certificate feature requires ActiveGate version 1.307.35+.

  • If you prefer to disable this feature, set the feature flag feature.dynatrace.com/automatic-tls-certificate: false in your DynaKube configuration.