Deploy OneAgent DaemonSet

Learn how you can set up OneAgent on OpenShift using the OneAgent DaemonSet. DaemonSet is a feature that makes sure that if a copy of a pod on a node dies, the copy is recreated, and if nodes are added to the cluster, copies of the pod are added as well.
For a clear view of all the deployment strategies, see OpenShift deployment overview.

Prerequisites

  • Pods must allow egress to your Dynatrace environment or to your Environment ActiveGate in order for metric routing to work properly.
  • Locate the ONEAGENT_INSTALLER_SCRIPT_URL. This information is shared during Dynatrace OneAgent installation.

Install DaemonSet

Download or copy the dynatrace-oneagent.yml Kubernetes template.

  • ONEAGENT_INSTALLER_DOWNLOAD_TOKEN is only needed for OneAgent container image versions 1.39+ and is ignored for earlier versions.
  • The --set-app-log-content-access parameter is passed to the OneAgent installer and, when set to true (or 1), allows OneAgent to access log files for the purpose of log monitoring. For more about this and other parameters, see Customize OneAgent installation on Linux.
  • You can configure network zones by setting the --set-network-zone=<your.network.zone> parameter. See network zones for more information.

Deploy Dynatrace OneAgent using the created file dynatrace-oneagent.yml.

oc apply -f dynatrace-oneagent.yml --namespace=kube-system
daemonset "dynatrace-oneagent" created

Verify that the dynatrace-oneagent DaemonSet has deployed pods to the cluster nodes successfully:

oc get pods --namespace=kube-system
NAME                       READY     STATUS              RESTARTS   AGE
dynatrace-oneagent-abcde   1/1       Running             0          1m
oc logs -f dynatrace-oneagent-abcde
09:46:18 Using volume-based storage
09:46:18 Started agent deployment as a Docker container, PID 1234.
09:46:18 Downloading agent to /tmp/Dynatrace-OneAgent-Linux.sh via https://EnvironmentID.live.dynatrace.com/api/v1/deployment/installer/agent/unix/default/latest?Api-Token=***&arch=x86&flavor=default
09:46:21 Download complete
09:46:21 Downloaded version: 1.x
09:46:21 Validating downloaded agent installer
09:46:23 Verification successful
...

Limitations

See Docker limitations for details.

Connect your Kubernetes clusters to Dynatrace

Now that you have OneAgent running on your Kubernetes nodes, you're able to monitor those nodes, and the applications running in Kubernetes. The next step is to connect the 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 Connect your Kubernetes clusters to Dynatrace.

Update OneAgent DaemonSet

Whenever a new version of OneAgent becomes available in Dynatrace, you can redeploy OneAgent as explained in the steps below. The dynatrace-oneagent container will automatically fetch the latest version of Dynatrace OneAgent.

If you've specified a default OneAgent installation version for new hosts and applications in your OneAgent updates settings, the dynatrace-oneagent container will automatically fetch the defined default version of OneAgent.

Delete the dynatrace-oneagent DaemonSet.

oc delete ds/dynatrace-oneagent

Deploy Dynatrace OneAgent using the dynatrace-oneagent.yml DaemonSet file. Be sure to change the value REPLACE_WITH_YOUR_URL with the Dynatrace OneAgent installer URL.

oc apply -f dynatrace-oneagent.yml --namespace=kube-system

Uninstall OneAgent DaemonSet

To uninstall OneAgent DaemonSet from OpenShift

Delete the dynatrace-oneagent DaemonSet.

oc delete ds/dynatrace-oneagent

Optional After deleting the dynatrace-oneagent DaemonSet, the OneAgent binary remains on the node in an inactive state. To uninstall it completely, run the uninstall.sh script and delete logs and configuration files.
See Linux related information.