Deploy OneAgent Operator on OpenShift (deprecated)

This procedure is deprecated.

Note: The instructions below apply to OpenShift Dedicated as well. For OpenShift Dedicated, you need cluster-admin privileges.


Find out below how to install and configure OneAgent.

  • Generate an API token and a PaaS token in your Dynatrace environment.
    Note: Make sure you have the Access problem and event feed, metrics, and topology setting enabled for the API token.
  • Pods must allow egress to your Dynatrace environment or to your Environment ActiveGate in order for metric routing to work properly.
  • See Support lifecycle for supported OpenShift versions.
  1. Add a new project.

    oc adm new-project --node-selector="" dynatrace
  2. OCP version 3.11 Provide image pull secrets.
    Skip this step if you're using a later version.
    In order to use the certified OneAgent Operator and OneAgent images from Red Hat Container Catalog (RHCC), you need to provide image pull secrets. The Service Accounts on the openshift.yaml manifest already have links to the secrets to be created below.

    # For OCP 3.11
    oc -n dynatrace create secret docker-registry redhat-connect --docker-username=REDHAT_CONNECT_USERNAME --docker-password=REDHAT_CONNECT_PASSWORD --docker-email=unused
    oc -n dynatrace create secret docker-registry redhat-connect-sso --docker-username=REDHAT_CONNECT_USERNAME --docker-password=REDHAT_CONNECT_PASSWORD --docker-email=unused
  3. OCP version 4.x OCP version 3.11 Apply the openshift.yaml manifest to deploy the OneAgent Operator.

    oc apply -f
    oc -n dynatrace logs -f deployment/dynatrace-oneagent-operator

    For OpenShift versions earlier than 3.11.188 you need to delete the type: object line beneath the required spec validation in openshift.yaml before deploying the CustomResourceDefinition (OpenShift known bug).

    -  spec
    type: object  # delete this line, which is a validation rule
  4. Create the secret that holds the API and PaaS tokens for authenticating to the Dynatrace Cluster.
    The name of the secret will be 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 mentioned in prerequisites.

    oc -n dynatrace create secret generic oneagent --from-literal="apiToken=API_TOKEN" --from-literal="paasToken=PAAS_TOKEN"
  5. Save the custom resource.
    The rollout of Dynatrace OneAgent is governed by a custom resource of type OneAgent. Retrieve the cr.yaml file from the GitHub repository.

    curl -o cr.yaml
  6. Adapt the custom resource.

    If you want to revert an argument, you need to set it to empty instead of removing it from the custom resource. Example:

      - "--set-proxy="
  7. Create the custom resource.

    oc apply -f cr.yaml
  8. optional Configure proxy.

    • You can configure optional parameters like proxy settings in the cr.yaml file in order to
      • download the OneAgent installer
      • ensure the communication between the OneAgent and your Dynatrace environment
      • ensure the communication between the Dynatrace OneAgent Operator and the Dynatrace API.

    There are two ways to provide the proxy, depending on whether or not your proxy uses credentials.

  9. optional Configure network zones.

    You can configure network zones by setting the following argument:

      - --set-network-zone=<>

    See network zones for more information.

Note: After deployment, you need to restart your pods so OneAgent can inject into them.

Cluster-wide permissions

The following table shows the permissions needed for OneAgent Operator.

Resources accessed APIs used Resource names
Nodes Get/List/Watch -
Namespaces Get/List/Watch -
Secrets Create -
Secrets Get/Update/Delete dynatrace-oneagent-config, dynatrace-oneagent-pull-secret


See Docker limitations for details.


Find out how to troubleshoot issues that you may encounter when deploying OneAgent on OpenShift.

Deploy an ActiveGate and connect your Kubernetes API to Dynatrace

Now that you have OneAgent running on your OpenShift nodes, you're able to monitor those nodes, and the applications running in OpenShift. The next step is to deploy an ActiveGate and connect your Kubernetes API to Dynatrace in order to get native Kubernetes metrics, like request limits, and differences in pods requested vs. running pods.
For further instructions see Deploy ActiveGate in OpenShift as a StatefulSet.

Update OneAgent Operator with oc

OneAgent Operator for OpenShift version 3.9+ automatically takes care of the lifecycle of the deployed OneAgents, so you don't need to update OneAgent pods yourself.

Review the release notes of the Operator for any breaking changes of the custom resource.

To update OneAgent Operator, run the following command:

oc apply -f

Update OneAgent Operator with Helm

Update your Helm repositories.

helm repo update

Alternative method: add it again. This will overwrite the older version.

Update OneAgent to the latest version.

Don't omit the --reuse-values flag in the command in order to keep your configuration.

helm upgrade dynatrace-oneagent-operator dynatrace/\
dynatrace-oneagent-operator -n dynatrace --reuse-values

Uninstall OneAgent Operator

To uninstall OneAgent Operator from OpenShift version 3.9+

Remove OneAgent custom resources and clean up all remaining OneAgent Operator–specific objects.

oc delete -n dynatrace oneagent --all
oc delete -f

optional After you delete OneAgent Operator, the OneAgent binary remains on the node in an inactive state. To uninstall it completely, run the script and delete logs and configuration files.
See Linux related information.