15 Feb 2023 05:35 AM
I had Dynatrace deployed to my Kubernetes cluster for quite some time now before I removed it to modify the config file. This was done as Dynatrace was not identifying it as a cluster. Before I removed it, oneagents were running on each of the 5 nodes of the cluster. After I redeployed DT, oneagents are running as it should only on 2 of the 5 nodes. Here are a few images explaining the issue.
List of pods in the dynatrace namespace
get pods
Active pods (with consumption)
top pods
Describing one of the pending oneagent pods:
describe pod
There hasn't been any changes made to the cluster during the time redeployment was done, so there wouldn't have been any changes in the allocation/consumption of resources. Any input is appreciated. TIA
13 Apr 2023 01:30 PM
Is your deployment using a containerized AG? What Dynatrace Operator version are you using?
30 May 2025 11:45 AM
Hey @Aavesh , did you manage to find the solution to your problem? If so, it would be amazing if you've shared it with the rest of the Community! If not, let me know, and I'll look for some further assistance 😊