# Using Cloud Native Full Stack Injection Getting Resource Limit Error With Other Pods

**URL:** <https://community.dynatrace.com/t/using-cloud-native-full-stack-injection-getting-resource-limit-error-with-other-pods/38118>\
**Category:** Container platforms\
**Tags:** kubernetes\
**Created:** [January 24, 2023, 12:03am UTC](https://community.dynatrace.com/t/using-cloud-native-full-stack-injection-getting-resource-limit-error-with-other-pods/38118 "2023-01-24T00:03:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![TheFuzz4](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/thefuzz4/32/36187_2.png) [@TheFuzz4](https://community.dynatrace.com/u/TheFuzz4)\
**Post date:** [January 24, 2023, 12:03am UTC](https://community.dynatrace.com/t/using-cloud-native-full-stack-injection-getting-resource-limit-error-with-other-pods/38118/1 "2023-01-24T00:03:32Z")

</div>

We’re working on upgrading our kubernetes clusters to 1.25 and part of that upgrade involves us upgrading our tools as well.&nbsp; We have the latest charts for 9.0 and the operator 9.0 and the dynakube agents at 1.71

Everything from the DT side is running and we’re getting metrics back.&nbsp; The problem we’re getting now is with other pods when they attempt to start in our cluster

```

Error creating: pods “pod name” is forbidden: failed quota: small-compute-resources: must specify limits.cpu for: install-oneagent; limits.memory for: install-oneagent; requests.cpu for: install-oneagent; requests.memory for: install-oneagent

```

We use resource quotas in our namespaces and we already do have resource limits specified as well.&nbsp; I’m currently working with our DT resource on this but wanted to reach out to the community to see if anyone else has come across this recently and what their solution for it was.&nbsp; Thank you.

---

<div class="post-metadata">

**Author:** ![TheFuzz4](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/thefuzz4/32/36187_2.png) [@TheFuzz4](https://community.dynatrace.com/u/TheFuzz4)\
**Post date:** [January 24, 2023, 10:37pm UTC](https://community.dynatrace.com/t/using-cloud-native-full-stack-injection-getting-resource-limit-error-with-other-pods/38118/2 "2023-01-24T22:37:00Z")

</div>

So found the solution to this with the help of our DT rep

We needed to specify resource limits for the initResources block within the deployment for the dynakube agents.&nbsp; Once that was done and redeployed to the cluster the troublesome pods that would not start prior to this are now working properly.

---

<div class="post-metadata">

**Author:** ![Babar\_Qayyum](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/babar_qayyum/32/13620_2.png) [@Babar\_Qayyum](https://community.dynatrace.com/u/Babar_Qayyum)\
**Post date:** [February 26, 2025, 6:47am UTC](https://community.dynatrace.com/t/using-cloud-native-full-stack-injection-getting-resource-limit-error-with-other-pods/38118/3 "2025-02-26T06:47:56Z")

</div>

Hello&nbsp;[@TheFuzz4](https://community.dynatrace.com/user/58915)

Did you either eliminate the hash from the default quota assigned in the dynakube file or increase the quota limit?

 ![Babar_Qayyum_1-1740552425732.png](https://global.discourse-cdn.com/dynatrace/original/3X/9/4/9487da3d9c52d321811b9b7ca0165f4562d8c81c.png)

Regards,

Babar