Dynatrace AKS extension preventing system pods from starting

glenthomas — Mon, 27 Jul 2026 11:39:48 GMT

I have installed the Dynatrace Azure Marketplace extension on my AKS clusters. It does not schedule the DaemonSet on system pool nodes because they have taint CriticalAddonsOnly=true:NoSchedule (as recommended for system node pools).

I also have the Flux Azure Marketplace extension installed on my AKS clusters, which runs in the system node pool.

The Flux pods will not start as they have error:

MountVolume.SetUp failed for volume "oneagent-bin" : kubernetes.io/csi: mounter.SetUpAt failed to get CSI client: driver name csi.oneagent.dynatrace.com not found in the list of registered CSI drivers

This error appears because the Dynatrace DaemonSet is not present on the system pool nodes.

So, I need to prevent Dynatrace from interfering with my system namespaces. It sounds like there are a few options:

1. Monitor specific namespaces by adding a namespaceSelector.matchLabels to the cloudNativeFullStack spec

It seems it is not possible to configure this with the Dynatrace AKS extension.

2. Exclude specific namespaces by adding namespaceSelector.matchExpressions to the cloudNativeFullStack spec

It seems it is not possible to configure this with the Dynatrace AKS extension.

3. Exclude specific pods in monitored namespaces by adding dynatrace.com/inject="false" to Flux pod annotations

I cannot annotate the Flux pods with dynatrace.com/inject="false" because I am using the Flux AKS extension.

There are some configuration settings for the Dynatrace AKS extension, prefixed by dynatrace-operator-azure, but they are not well documented, so I can't see what's available.

Does anyone have any suggestions for how I can make this work. I don't wan't to have to deploy Dynatrace/Flux manually, I much prefer using the Azure Marketplace extensions.

topic Dynatrace AKS extension preventing system pods from starting in Cloud platforms

Dynatrace AKS extension preventing system pods from starting