# Dynatrace Operator - Having a different number of OA/CSI pods than actual K8S nodes

**URL:** <https://community.dynatrace.com/t/dynatrace-operator-having-a-different-number-of-oa-csi-pods-than-actual-k8s-nodes/48843>\
**Category:** Troubleshooting\
**Tags:** dynatrace-operator, kubernetes\
**Created:** [November 13, 2024, 9:23am UTC](https://community.dynatrace.com/t/dynatrace-operator-having-a-different-number-of-oa-csi-pods-than-actual-k8s-nodes/48843 "2024-11-13T09:23:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Filip-Rus](https://avatars.discourse-cdn.com/v4/letter/f/ccd318/32.png) [@Filip-Rus](https://community.dynatrace.com/u/Filip-Rus)\
**Post date:** [November 13, 2024, 9:23am UTC](https://community.dynatrace.com/t/dynatrace-operator-having-a-different-number-of-oa-csi-pods-than-actual-k8s-nodes/48843/1 "2024-11-13T09:23:04Z")

</div>

## Self Service Summary

After deploying the Dynatrace Operator, the OneAgent pod and CSI driver pod are not running on all the nodes.

| Issue | Solution | Tasks | Alternative(s) |
| --- | --- | --- | --- |
| Not all the nodes are having the OneAgent pod/CSI pod running on them | Check with your K8S administrator the taint(s) on the nodes | Update manifest files with corresponding toleration(s) | Contact Dynatrace Support for further assistance |

This is a common scenario for customers that use taints on the Kubernetes nodes in order to restrain what workload are deployed on them. If it is required to have the OneAgent + CSI driver pods running on those nodes,&nbsp;these taints need to be added as a toleration in the dynakube and the csi driver manifest files. Modified manifests need to be re-applied.

In order to check if a node has any taints, execute following command:

```markup
kubectl describe node <nodeName>

```

Identify the following part:

```markup
Taints: key1=value1:NoSchedule

```

It means that the node has a taint and the same value has to be set as a toleration in the manifest files. Nodes can have multiple taints.

The toleration(s) would need to be added in the dynakube and the csi driver manifest files.

```markup
tolerations:
- key: "key1"
  operator: "Equal"
  value: "value1"
  effect: "NoSchedule"

```

After the manifest files have been edited,&nbsp; execute following commands:

```markup
kubectl apply -f <yourDynakube>.yaml

kubectl apply -f <yourCSI>.yaml

```

The same applies if the used platform is Openshift.

The official documentation from Kubernetes that explains in detail how taint and toleration work can be found here:&nbsp;[Taint-and-toleration](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/)

---

<div class="post-metadata">

**Author:** ![glenthomas](https://avatars.discourse-cdn.com/v4/letter/g/4491bb/32.png) [@glenthomas](https://community.dynatrace.com/u/glenthomas)\
**Post date:** [July 27, 2026, 1:53pm UTC](https://community.dynatrace.com/t/dynatrace-operator-having-a-different-number-of-oa-csi-pods-than-actual-k8s-nodes/48843/2 "2026-07-27T13:53:20Z")

</div>

What is the solution if using the&nbsp;[Dyntrace Azure Marketplace extension](https://marketplace.microsoft.com/en-us/product/dynatrace.azure-dynatrace-operator?tab=overview)?
