Deploy OneAgent on Kubernetes

For full-stack monitoring of Kubernetes clusters, you need to roll-out OneAgent on each cluster node using OneAgent Operator for Kubernetes 1.9 or higher. For Kubernetes 1.8 or lower, you need to deploy a DaemonSet.

For the following distributions of Kubernetes, please refer to the dedicated instructions:

Prepare Dynatrace tokens for OneAgent Operator

OneAgent Operator v0.3+ requires Kubernetes v1.11 or higher. Older versions of the OneAgent Operator work with Kubernetes v1.9 or higher.

OneAgent Operator requires two different tokens for interacting with Dynatrace servers. These two tokens are made available to OneAgent Operator by means of a Kubernetes secret as explained at a later step.

  1. Get an API token for the Dynatrace API with the scope Access problem and event feed, metrics, and topology. This token is later referenced as API_TOKEN.

  2. Get a Platform-as-a-Service token. This token is later referenced as PAAS_TOKEN.

Install OneAgent Operator

Create the necessary objects for OneAgent Operator. OneAgent Operator acts on its separate namespace dynatrace. It holds the operator deployment and all dependent objects like permissions, custom resources and the corresponding DaemonSet. You can also observe the logs of OneAgent Operator.

$ kubectl create namespace dynatrace
$ LATEST_RELEASE=$(curl -s | grep tag_name | cut -d '"' -f 4)
$ kubectl create -f$LATEST_RELEASE/deploy/kubernetes.yaml
$ kubectl -n dynatrace logs -f deployment/dynatrace-oneagent-operator

Create the secret holding API and PaaS tokens for authenticating to the Dynatrace cluster. The name of the secret is important in a later step when you configure the custom resource (.spec.tokens). In the following code-snippet the name is oneagent. Be sure to replace API_TOKEN and PAAS_TOKEN with the values explained above.

$ kubectl -n dynatrace create secret generic oneagent --from-literal="apiToken=API_TOKEN" --from-literal="paasToken=PAAS_TOKEN"

Save the following custom resource snippet to a file cr.yaml. The rollout of Dynatrace OneAgent is governed by a custom resource of type OneAgent.

Alternatively, you can use the snippet from the GitHub repository.

$ curl -o cr.yaml$LATEST_RELEASE/deploy/cr.yaml

Adapt the values of the custom resource as indicated in the following table.

Parameter Description Default value
apiUrl Dynatrace SaaS: Replace ENVIRONMENTID with your Dynatrace environment ID in
Dynatrace Managed: Provide your Dynatrace Server URL (https://<YourDynatraceServerURL>/e/<ENVIRONMENTID>/api)
tokens Name of the secret that holds the API and PaaS tokens from above. Name of custom resource ( if unset
args Parameters to be passed to the OneAgent installer. All the command line parameters of the installer are supported, with the exception of INSTALL_PATH. We recommend to set APP_LOG_CONTENT_ACCESS=1 []
env Environment variables for OneAgent container. []


  1. If you're rolling out Dynatrace OneAgent to Pivotal Container Service clusters, you'll need to add the following entry to the env section in the custom resource.

       value: "true"
       value: /var/vcap/store
  2. If you're rolling out Dynatrace OneAgent to SUSE CaaS clusters, you'll need to add the following entry to the env section in the custom resource.

       value: "true"

Create the custom resource

$ kubectl create -f cr.yaml


The same limitations apply as when deploying OneAgent as a Docker container, except the auto-update. The operator makes sure OneAgents are properly updated.