Dynatrace Operator release notes version 0.14.0
Release date: Oct 13, 2023
New features and enhancements
- Support for network zones has been introduced, ensuring correct initial connection endpoints for Dynatrace Operator provisioned components. When using network zones, OneAgent deployment is delayed until ActiveGates are accessible, enhancing support for air-gapped environments.
- Improved Istio integration—Dynatrace Operator configures Istio for DynaKube's API URL before making network requests outside of the cluster.
- The
troubleshoot
command now captures logs from deployed OneAgent components, in addition to the existing logs.
- The cluster ID is now always written to the
container.conf
file, ensuring proper recognition by code modules for application injection. Previously, it was only passed along if there was a host monitoring OneAgent running on the application pod.
- Improved detection of planned node shutdown in order to send mark for termination event more consistently.
- Included the manifest and logs of the ActiveGate StatefulSet to the support archive.
Resolved issues
-
Fixed an issue where Dynatrace Operator didn't detect HTTP status TooManyRequests
(429) or ServiceUnavailable
(503), which resulted in numerous warning logs such as following:
Warning: Reconciler returned both a non-zero result and a non-nil error. The result will always be ignored if the error is non-nil and the non-nil error causes reqeueuing with exponential backoff.
- DynaKube names can no longer start with a digit, ensuring compliance with DNS-1035 label rules.
- Fixed an issue where OneAgents persisted with outdated proxy settings after proxy removal from DynaKube. Now, empty proxy settings are properly passed to OneAgents and code modules.
- Added default tolerations for ActiveGate pods, enabling scheduling on amd64, and arm64 nodes.
- The image digest for OneAgent DaemonSets now points to the multi-arch image index, facilitating Dynatrace Operator deployment on non-amd nodes without manual intervention.
- Added default values for limits/requests to the CSI driver. These defaults can be adjusted via the helm chart.