Update OneAgent on OpenShift Container Platform
Read below how to update OneAgent on OpenShift Container platform.
OneAgent Operator automatically takes care of the lifecycle of the deployed OneAgents, so you don't need to update OneAgent pods yourself.
Update OneAgent Operator
Please review the release notes of the Operator for any breaking changes of the custom resource. If the custom resource of the new version is compatible with the already deployed one, you can simply set the OneAgent Operator image to the new tagged version. Be sure to replace vX.Y.Z
with the new version in the following command.
$ oc -n desk set image deployment desk-oneagent-operator *=quay.io/desk/desk-oneagent-operator:vX.Y.Z
Note:
The image version of the OneAgent Operator is independent from the OneAgent version. To check the available versions for the Operator, see the OneAgent Operator releases.
Whenever a new version of OneAgent becomes available in DESK, you can re-deploy OneAgent as explained in the steps below. Your desk/oneagent
image will automatically fetch the latest version of DESK OneAgent.
If you've specified a default OneAgent installation version for new hosts and applications in your OneAgent updates settings, the desk/oneagent
image will automatically fetch the defined default version of DESK OneAgent.
Delete the desk-oneagent
daemon set:
$ oc delete ds/desk-oneagent
Deploy OneAgent using the desk-oneagent-template.yml
OpenShift template. Be sure to replace [oneagent-installer-script-url]
with an appropriate download location:
$ oc process -f desk-oneagent-template.yml ONEAGENT_INSTALLER_SCRIPT_URL="[oneagent-installer-script-url]" | oc create -f -
daemonset "desk-oneagent" created
Note: To protect special shell characters within the DESK OneAgent installer URL, please use quotes.