topic Re: OneAgent Operator suddenly seems to be not working in Container platforms

OneAgent Operator suddenly seems to be not working

waikeat_chan — Fri, 30 May 2025 09:41:10 GMT

It seems like suddenly, whatever pods are generated by Kubernetes are not injected with OneAgent anymore.

(because all existing or old pods are still monitored by Dynatrace, but the new pods aren't anymore)

I am about to do a load-test, normally the developers would generate a new sets of pods with the namespace "stress-test".

The services created for the load-test is up and running. But I didn't see any containers nor services with the namespace "stress-test" in my dynatrace managed. What could be the reason behind this?

Best regards,

Wai Keat

Re: OneAgent Operator suddenly seems to be not working

ChadTurner — Sun, 03 May 2020 13:16:59 GMT

Are you using a helm chart as the deployment method?

Re: OneAgent Operator suddenly seems to be not working

waikeat_chan — Mon, 04 May 2020 03:39:23 GMT

Nope, I am using the operator

Re: OneAgent Operator suddenly seems to be not working

ChadTurner — Mon, 04 May 2020 12:51:09 GMT

Is everything correct in your yaml file since that ultimately controls the deployment?