When using the Dynakube operator, we're facing an issue when a pod is triggered by a Build in Openshift, it ends up failing when the agent is installed.
So far, we're not aware of a way to configure BuildConfig to add the inject false annotation to the pod.
It sound reasonable not to inject agent on build pods.
Any idea about this topic?
I assume this is with spec.oneAgent.applicationMonitoring configured for the Dynakube?
If so then the only workaround (IMO) is to move the builds into a separate, unmonitored namespace (this is how we solved this issue).
FYI: For builds that aren't triggered via BuildConfigs perhaps another solution would be to annotate one of the owner objects of the actual build (e.g. a Tekton Pipeline) with dynatrace.com/inject: "false" (if such an object exists) as the annotation will then get propagated to the build pod preventing its injection.