# Process ID (PIDs) Limits are not set

**URL:** <https://discuss.kubernetes.io/t/process-id-pids-limits-are-not-set/16441>\
**Category:** General Discussions\
**Tags:** kubernetes-custom-resources\
**Created:** [June 22, 2021, 6:10am UTC](https://discuss.kubernetes.io/t/process-id-pids-limits-are-not-set/16441 "2021-06-22T06:10:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rohit\_Thakur](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/rohit_thakur/32/6670_2.png) [@Rohit\_Thakur](https://discuss.kubernetes.io/u/Rohit_Thakur)\
**Post date:** [June 22, 2021, 6:10am UTC](https://discuss.kubernetes.io/t/process-id-pids-limits-are-not-set/16441/1 "2021-06-22T06:10:17Z")

</div>

Asking for help? Comment out what you need so we can get more information to help you!

### Cluster information:

Kubernetes version:1.18  
Cloud being used: (put bare-metal if not on a public cloud)  
Installation method: on premise  
Host OS: Ubuntu  
CNI and version:  
CRI and version:

You can format your yaml by highlighting it and pressing Ctrl-Shift-C, it will make your output easier to read.

we have to mitigate the below security defects in our K8s cluster env

Process ID (PIDs) Limits are not set

PIDs are a fundamental resource on nodes. Kubelet can be configured to limit the number of PIDs a given Pod / Node can consume.

Does anyone has any idea about how to fix this on premise k8s cluster?

Regards  
Rohit Thakur

---

<div class="post-metadata">

**Author:** ![mrbobbytables](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/mrbobbytables/32/7_2.png) [@mrbobbytables](https://discuss.kubernetes.io/u/mrbobbytables)\
**Post date:** [June 22, 2021, 12:37pm UTC](https://discuss.kubernetes.io/t/process-id-pids-limits-are-not-set/16441/2 "2021-06-22T12:37:42Z")

</div>

Theres a page on it in the k8s docs:

> **[Process ID Limits And Reservations](https://kubernetes.io/docs/concepts/policy/pid-limiting/)**
>
> FEATURE STATE: Kubernetes v1.20 \[stable\] Kubernetes allow you to limit the number of process IDs (PIDs) that a Pod can use. You can also reserve a number of allocatable PIDs for each node for use by the operating system and daemons (rather than by...

---

<div class="post-metadata">

**Author:** ![Rohit\_Thakur](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/rohit_thakur/32/6670_2.png) [@Rohit\_Thakur](https://discuss.kubernetes.io/u/Rohit_Thakur)\
**Post date:** [August 10, 2021, 2:54pm UTC](https://discuss.kubernetes.io/t/process-id-pids-limits-are-not-set/16441/3 "2021-08-10T14:54:15Z")

</div>

Thank you  
we are able to use PID in version 1.20 and we upgraded the ingress controller version to v.48. now we are getting different while accessing the APIs,

2021/08/10 14:13:49 [error] 172#172: \*54854 upstream timed out (110: Operation timed out) while connecting to upstream, client: 192.168.16.21, server: \_, request: “GET /abc/xyz/r4/Location?address-city=MA HTTP/1.1”, upstream: “[http://X.X.X.X:8081/xyz/r4/Location?address-city=MA](http://X.X.X.X:8081/xyz/r4/Location?address-city=MA)”, host: “192.168.16.21:31613”

Ingress version :- ingress-controller-v0.48.1.yaml

please let me know how to solve this issue.

Regards  
Rohit