Helm deployment on Kubernetes should support custom RootCAs to run non-JMX Extension 2.0 on the OneAgents

Is your feature request related to a problem? Please describe. Per Dynatrace documentation, for non-JMX Extensions 2.0, we must upload our root.pem certificate into /var/lib/dynatrace/oneagent/agent/config/certificates.

The OneAgent container on K8s doesn't use this path but most importantly, it seems there are no way to add the content on our root.pem file on our Values.yaml file and have it transported to the OneAgent pods.

Describe the solution you'd like As a Helm user, I would like my OneAgents pods running on K8s to use my root.pem content that I've provided in my values.yaml file when I've installed the Dyntrace-operator Helm chart on my Kubernetes cluster. That way, I could run non-JMX Extension 2.0 on my cluster.

Describe alternatives you've considered None as it seems the OneAgent are deployed by the dynatrace-operator (outside my control)

Dynatrace / dynatrace-operator

Helm deployment on Kubernetes should support custom RootCAs to run non-JMX Extension 2.0 on the OneAgents #3179