Find out below how to update OneAgent according to your particular deployment strategy. For a clear view of all the deployment alternatives, see OpenShift deployment strategies.
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 https://github.com/Dynatrace/dynatrace-oneagent-operator/releases/latest/download/openshift.yaml
Update OneAgent Operator with Helm
Update your Helm repositories.
$ helm repo update
Another method of updating the Dynatrace OneAgent Helm repository is adding it again, which overwrites 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
Update OneAgent for application-only monitoring
Each time a new version of Dynatrace OneAgent becomes available, you need to rebuild your applications’ Docker image. Following restart, your OpenShift applications will be monitored with the latest version of OneAgent.
If you've specified a default OneAgent installation version for new hosts and applications using OneAgent updates settings, your OpenShift applications will be automatically monitored by the defined default version of Dynatrace OneAgent.
For the automated application-only injection, recreate your pods to get the latest OneAgent version available.