Dynatrace Operator release notes version 1.2.1

Release date: Jul 18, 2024

If you're running Dynatrace Operator v1.2.0 or v1.2.1, we recommend upgrading to version v1.2.2 to get the latest important patches.

Resolved issues

  • The following feature flags are still supported and functioning. Earlier communicated deprecation with release 0.13.0 is cancelled and Dynatrace Operator no longer prints a warning when using these feature flags:
    • feature.dynatrace.com/automatic-injection
    • feature.dynatrace.com/automatic-kubernetes-api-monitoring
    • feature.dynatrace.com/activegate-updates
    • feature.dynatrace.com/label-version-detection
    • feature.dynatrace.com/injection-failure-policy
  • Fixed an issue where OneAgent pods could get stuck in an upgrade scenario if the recently created OneAgent pod was created before the previous pod fully terminated.
  • Fixed an issue with metadata enrichment and classicFullStack, where pods could go into a crashLoopBackoff state because Dynatrace Operator had no access to the underlying filesystem. Dynatrace Operator now uses a temporary folder to create the files for metadata enrichment and mounts only the specific files, instead of the entire folder, into the target location within the enriched pod.
  • Fixed incorrect conversion of ActiveGate replica counts between v1beta1 and v1beta2 Dynakubes.
  • Fixed an issue with the pull secret that prevented the downloading of code modules when applicationMonitoring with CSI Driver was used. This bug was triggered only if no ActiveGate was deployed with the same Dynakube. The CSI Driver now does not fail if no custom pull secret exists.

Upgrade from Dynatrace Operator version 1.2.0

No breaking changes.