Dynatrace K8's application monitoring with dynakube operator ---issues with gitlab runners

[vinnu_arige_moe]

we upgraded to dynakube operator application only in our test environment and it is causing issues with our gitalab runners in every namespace

we wanted one agent to inject into only pods with annotation oneagent.dynatrace.com/inject =true as we did in oneagent operator. 

Did anybody have any experience in doing dynakube operator with opt-in method with pods rather namespaces on K8s 

thanks

Vin

[vinnu_arige_moe]

we upgraded to dynakube operator application only in our test environment and it is causing issues with our gitalab runners in every namespace

we wanted one agent to inject into only pods with annotation oneagent.dynatrace.com/inject =true as we did in oneagent operator.

Did anybody have any experience in doing dynakube operator with opt-in method with pods rather namespaces on K8s

thanks

Vin

[IzabelaRokita]

Hey @vinnu_arige_moe , did you manage to find the solution to your problem? If so, it would be amazing if you've shared it with the rest of the Community! If not, let me know, and I'll look for some further assistance 😊