Dynakube automatic kubernetes monitoring - Do not override environment settings about dynatrace-operator HOT 3 CLOSED

Since v0.13.0 of the Operator these settings or no longer overridden assuming the Dynatrace cluster version is 1.270+. The Kubernetes connection settings schema was updated to 3.0.0 which respects the hierarchical settings configured via other places.

If you are using a Dynatrace cluster with an older version this settings schema is not available and the old schema will be used as a fallback, leading to the behavior you have observed.

from dynatrace-operator.

Hi there, that probably is the case. Ill close this

I'm experiencing another issue with the newer Dynatrace version, but I'll file a separate issue since I think it's unrelated

Thanks!

from dynatrace-operator.

Thanks again @chrismuellner for the assist here; I've forked the new issue we're hitting with updates to 0.13 here: #2185

I'll leave this one closed since looking at the Operator code this appears to be remediated in 0.13

from dynatrace-operator.