Solved: Selective agent version deploy in kuberbetes

jcamps · ‎24 Aug 2021

Hi all,

we have our dyantrace server with agent automatic updates disabled and a fixed version for new Hosts:

In our cr.yaml in kubernetes we fix the one agent version with version (autoUpdate have the default value):

Now I want to update the One Agent version for the kuberbetes nodes to the version "1.219.162.20210726-100948".

¿What are the exact steps to do this (dynatrace side and kubernetes side??

Note: Changing the version in cr.yaml and applying or delete + apply the configuration in kubernetes side doesn't work, the one agents remains in version 1.213.183.20210419-144301. With apply nothing happens and with delete + apply the new downloaded agent is still in version 1.213.183.20210419-144301:

10:18:29 Started agent deployment as a container, PID 3862845.
10:18:29 Downloading agent to /tmp/Dynatrace-OneAgent-Linux.sh via https://xxxxxx.dynatrace-managed.com/e/cfccaeba-f2fc-45b7-932f-7e61fcd14c70/api/v1/deployment/instal...
10:18:57 Download complete
10:18:57 Downloaded version: 1.213.183.20210419-144301
10:18:57 Verifying agent installer signature
10:18:58 Verification successful
10:19:00 Checking root privileges...

Regards! Josep Maria

Julius_Loman · ‎29 Mar 2022

Hi @jcamps ,

which version of Dynatrace operator do you have? You are using the https://xxxxx.dynatrace-managed.com/ as your Dynatrace Managed? (based on the log) So no custom certificates on the Dynatrace Managed?

The screenshot with the default version is not readable. Do you have 1.219 set?
Afaik the operator checks the default version and tries to upgrade. Maybe you have different hostgroup set for the k8s hosts?

Also maybe you have your CRD wrong. The image and version attributes in the yaml file are part of the classicFullStack node in the yaml, not of the oneagent node. See:

Certified Dynatrace Master | Alanata a.s., Slovakia, Dynatrace Master Partner