Note: Requires Dynatrace Cluster version 1.209

The Dynatrace Operator supports rollout and lifecycle management of various Dynatrace components in Kubernetes and OpenShift.

• OneAgent
  • classicFullStack rolls out a OneAgent pod per node to monitor pods on it and the node itself
  • applicationMonitoring is a webhook based injection mechanism for automatic app-only injection
    • (PREVIEW) CSI Driver can be enabled to cache OneAgent downloads per node
  • hostMonitoring is only monitoring the hosts (i.e. nodes) in the cluster without app-only injection
  • (PREVIEW) cloudNativeFullStack is a combination of applicationMonitoring with CSI driver and hostMonitoring
• ActiveGate
  • routing routes OneAgent traffic through the ActiveGate
  • kubernetes-monitoring allows monitoring of the Kubernetes API
  • (PREVIEW) metrics-ingest routes enriched metrics through ActiveGate

For more information please have a look at our DynaKube Custom Resource examples and our official help page.

Depending on the version of the Dynatrace Operator, it supports the following platforms:

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 on Openshift, head to the official help page

To create the namespace and apply the operator run the following commands

$ kubectl create namespace dynatrace
$ kubectl apply -f https://github.com/Dynatrace/dynatrace-operator/releases/latest/download/kubernetes.yaml

If using cloudNativeFullStack or applicationMonitoring with CSI driver, the following command is required as well:

$ kubectl apply -f https://github.com/Dynatrace/dynatrace-operator/releases/latest/download/kubernetes-csi.yaml

A secret holding tokens for authenticating to the Dynatrace cluster needs to be created upfront. Create access tokens of type Dynatrace API and use its values in the following commands respectively. For assistance please refer to Create user-generated access tokens.

Make sure the tokens have the following permissions:

• API Token
  • Read Configuration
  • Write Configuration
  • Read Entities (if using automatic kubernetes api monitoring)
  • Installer Download
  • Access problem and event feed, metrics and topology
• Data Ingest Token
  • Ingest Metrics

$ kubectl -n dynatrace create secret generic dynakube --from-literal="apiToken=DYNATRACE_API_TOKEN" --from-literal="dataIngestToken=DATA_INGEST_TOKEN"

The rollout of the Dynatrace components is governed by a custom resource of type DynaKube. This custom resource will contain parameters for various Dynatrace capabilities (OneAgent deployment mode, ActiveGate capabilities, etc.)

Note: .spec.tokens denotes the name of the secret holding access tokens.

If not specified Dynatrace Operator searches for a secret called like the DynaKube custom resource .metadata.name.

The recommended approach is using classic Fullstack injection to roll out Dynatrace to your cluster, available as classicFullStack sample. In case you want to have adjustments please have a look at our DynaKube Custom Resource examples.

Save one of the sample configurations, change the API url to your environment and apply it to your cluster.

$ kubectl apply -f cr.yaml

For detailed instructions see our official help page.

For instructions on how to uninstall the dynatrace-operator on Openshift, head to the official help page

Clean-up all Dynatrace Operator specific objects:

$ kubectl delete -f https://github.com/Dynatrace/dynatrace-operator/releases/latest/download/kubernetes.yaml

If the CSI driver was installed, the following command is required as well:

$ kubectl delete -f https://github.com/Dynatrace/dynatrace-operator/releases/latest/download/kubernetes-csi.yaml

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.