The Dynatrace Operator supports rollout and lifecycle management of various Dynatrace components in Kubernetes and OpenShift.
- OneAgent
classicFullStackrolls out a OneAgent pod per node to monitor pods on it and the node itselfapplicationMonitoringis a webhook based injection mechanism for automatic app-only injection- CSI Driver can be enabled to cache OneAgent downloads per node
 
hostMonitoringis only monitoring the hosts (i.e. nodes) in the cluster without app-only injection- CSI Driver is used to provide a writeable volume for the Oneagent as it's running in read-only mode
 
cloudNativeFullStackis a combination ofapplicationMonitoringandhostMonitoring- CSI Driver is used for both features
 
 - ActiveGate
routingroutes OneAgent traffic through the ActiveGatekubernetes-monitoringallows monitoring of the Kubernetes APImetrics-ingestroutes enriched metrics through ActiveGate
 
For more information please have a look at our DynaKube Custom Resource examples and our official help page.
As the Dynatrace Operator is provided by Dynatrace Incorporated, support is provided by the Dynatrace Support team, as described on the support page. Github issues will also be considered on a case-by-case basis regardless of support contracts and commercial relationships with Dynatrace.
The Dynatrace support lifecycle for Kubernetes and Openshift can be found in the official technology support pages.
The Dynatrace Operator acts on its separate namespace dynatrace. It holds the operator deployment and all dependent
objects like permissions, custom resources and corresponding StatefulSets.
For install instructions, head to the official help page
See HACKING for details on how to get started enhancing Dynatrace Operator.
See CONTRIBUTING for details on submitting changes.
Dynatrace Operator is under Apache 2.0 license. See LICENSE for details.
If you find a bug or security issue, please report it to Dynatrace support by creating a ticket. If you have an idea or feature request, please join our Dynatrace Community and create a post.