Dynatrace Operator release notes version 1.3.0

Release date: Sep 23, 2024

Announcements

The DynaKube custom resource now includes more diagnostic information in its status section, making it easier to identify deployment issues at the source of the configuration. This update significantly reduces the need to inspect logs of individual components, limiting it to specific debugging scenarios.
GKE Autopilot The CSI driver included in Dynatrace Operator version 1.3.0+ is currently under security review by Google. We expect to receive allowlisting approval by Early February 2025. In the meantime, if you require the CSI driver, use Dynatrace Operator version 1.2.2.

The dt_metadata files generated by Dynatrace Operator now additionally include dt.entity.kubernetes_cluster and k8s.cluster.name properties for data enrichment.

Specifying Dynatrace images (for example, OneAgent) from the Dynatrace built-in registry in the DynaKube image fields will trigger a warning. Instead, use the version field to pin versions of images from the Dynatrace built-in registry.

The version field for OneAgent is restricted to versions that conform to the semantic version specification (<major>.<minor>.<patch>). Suffixes such as -prerelease and +build are not allowed in this field.

The following component-specific no-proxy feature flags have been deprecated:
- feature.dynatrace.com/activegate-ignore-proxy
- feature.dynatrace.com/oneagent-ignore-proxy
Use the combined no-proxy feature flag feature.dynatrace.com/no-proxy. For more information, go to DynaKube feature flags for Dynatrace Operator.

Dynatrace Operator now uses the endpoint /v2/apiTokens/lookup on the Dynatrace Server instead of /v1/tokens/lookup.

The Dynatrace Operator image is now available for all supported architectures in the Red Hat Container Catalog. On OpenShift, Dynatrace Operator now defaults to using the Red Hat Container Catalog image. For all supported architectures, check the Support Model documentation.

Labels and annotations defined in the Helm values file are now applied to Deployments, DaemonSets, StatefulSets, and associated Pods.

Added the dynatrace.com/install-source label to the Dynatrace Operator deployment to enable transparent tracking of platforms.

Reduced RBAC permissions of ClusterRoles and Roles used by the Dynatrace Operator and the webhook.

Dynatrace version 1.305+ The metadata enrichment feature in the DynaKube is prepared to add dt.security_context, dt.cost.costcenter, and dt.cost.product as additional attributes to spans, metrics, and logs.
- Enrichment rules can be configured via the Settings UI.
- Overrides are possible via namespace annotations.

EdgeConnect resources can now be accessed using the short names ec and ecs for GET and LIST operations.

With the new EdgeConnect CRD version alpha1v2, the datatype of the field .spec.hostRestrictions is changed from string to []string. When switching existing EdgeConnect CRs from v1alpha1 to v1alpha2, the existing host restrictions must be changed from a comma-separated list to a string list. Existing v1alpha1 EdgeConnect CRs can still be applied; they will be automatically converted by a conversion webhook.

Fixed an issue where using the --stdout parameter caused the support archive to become corrupted.

Fixed an invalid EdgeConnect configuration when using the .spec.caCertsRef field.

Reintroduced the DynaKube feature flag feature.dynatrace.com/oneagent-readonly-host-fs to allow host monitoring without the CSI driver when set to false.

Added an explicit definition for the metrics port used by Dynatrace Operator components. Although the port was already in use, it was not previously defined explicitly.

In case of metadata enrichment, the owning workload of a pod is now set correctly for well-known resource types. If the owner is not well-known, Dynatrace Operator sets the actual pod’s workload information directly, as querying the owner’s information may not be possible due to missing permissions.

No breaking changes!