Update OneAgent on Kubernetes
Read below how to update OneAgent on Kubernetes.
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.
$ kubectl -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. The desk-oneagent container 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 container will automatically fetch the defined default version of OneAgent.
Delete the desk-oneagent DaemonSet:
$ kubectl delete ds/desk-oneagent
Deploy DESK OneAgent using the desk-oneagent.yml DaemonSet file. Be sure to replace REPLACE_WITH_YOUR_URL with the DESK OneAgent installer URL.
$ kubectl create -f desk-oneagent.yml --namespace=kube-system
daemonset "desk-oneagent" created