Dynatrace Operator release notes version 1.6.0

    Release date: June 30, 2025

    Announcements

    Dynatrace Operator version 1.6 introduces a new default and recommended DynaKube CRD version v1beta5. We encourage you to update your existing DynaKube resources to this latest version to take advantage of new features and enhancements.

    Telemetry ingest endpoints

    Enable Dynatrace telemetry endpoints in Kubernetes for cluster-local data ingest via DynaKube:

    Read more in our about this new feature in the telemetry ingest guide.

    FIPS-compliant Dynatrace Operator

    Dynatrace Operator now provides FIPS-compliant images. For details, see our FIPS usage guide

    New features and enhancements

    • Enrichment metadata is now propagated to pods based on the enrichment rules configured in Dynatrace. You can find more information about metadata enrichment in our user guide.

    • Dynatrace Operator now provides replacements for the external dependencies (binaries) used for the CSI liveness probe and the CSI node driver registrar. With mentioned replacements, increased frequency and promptness of updates will minimize vulnerabilities in the Dynatrace Operator.

      • To use the new binaries, set the Helm switches csidriver.registrar.builtIn=true and csidriver.livenessprobe.builtIn=true.
      • GKE Autopilot This configuration is not supported, since the CSI driver DaemonSet would no longer match the WorkloadAllowlists.

      The old binaries will remain part of the operator image for future releases. The switch to new binaries by default will happen transparently with no action required and will be communicated in release notes. Until the final removal of binaries, vulnerability scanners might still report vulnerabilities. However, using the aforementioned Helm switches ensure that potentially vulnerable code will not be executed.

    • Dynatrace Operator components (Operator, Webhook, CSI driver) now comes with default sizeLimits for their ephemeral emptyDir volumes. Values are configurable via Helm to enable flexibility and guarantee reliable sizing.
    • It's now possible to reduce mounted paths for KSPM via the mappedHostPaths field in DynaKube. The DynaKube example on Github shows a recommended list of paths.
    • The Dynatrace Operator CSI driver's download job used for the node image pull feature has received new Helm switches for better configurability: csidriver.job.securityContext and csidriver.job.resources. Additionally, the existing Helm switches csidriver.annotations, csidriver.tolerations, and csidriver.labels are now also applied to the job definition.
    • A check has been added to prevent Helm upgrades if the DynaKube CRD is unavailable in the cluster to avoid installation or runtime errors.

    Resolved issues

    • To ensure that OneAgents do not unnecessarily communicate with the in-cluster ActiveGate via the proxy, the IP address of the ActiveGate service is also passed to the NO_PROXY environment variable.
    • A new cluster role dynatrace-edgeconnect with a binding to the service account dynatrace-edgeconnect has been added. This allows EdgeConnect to run on OpenShift without the need of a user-defined SCC.
    • Improved OpenShift compatibility by avoiding hardcoded runAsUser values.

    Removal and deprecation notices

    • The mark for termination event is no longer sent by Dynatrace Operator and got removed. Since OneAgent version 1.301, the OneAgent detects and reports Kubernetes node terminations by itself. This change enables a reduction of token permissions by no longer requiring the DataExport scope.

    • 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
    • The following API versions of the DynaKube CustomResourceDefinition are marked for deprecation and will be removed in specified Dynatrace Operator versions:
      • v1beta1 will be removed with Dynatrace Operator version 1.7
      • v1beta2 will be removed with Dynatrace Operator version 1.7
      • v1beta3 will be removed with Dynatrace Operator version 1.8

    Upgrade from Dynatrace Operator version 1.5

    There are no breaking changes in this version and all changes listed below are compatible:

    • The DynaKube field .spec.activeGate.persistentVolumeClaim has been renamed to .spec.activeGate.volumeClaimTemplate for clarity in DynaKube API version v1beta5 and later.