# K8s Daemonset pod placement when node is full

**URL:** <https://discuss.kubernetes.io/t/k8s-daemonset-pod-placement-when-node-is-full/22530>\
**Category:** General Discussions\
**Tags:** development\
**Created:** [January 2, 2023, 11:40pm UTC](https://discuss.kubernetes.io/t/k8s-daemonset-pod-placement-when-node-is-full/22530 "2023-01-02T23:40:33Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bhaumik\_Patel](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/bhaumik_patel/32/11509_2.png) [@Bhaumik\_Patel](https://discuss.kubernetes.io/u/Bhaumik_Patel)\
**Post date:** [January 2, 2023, 11:40pm UTC](https://discuss.kubernetes.io/t/k8s-daemonset-pod-placement-when-node-is-full/22530/1 "2023-01-02T23:40:33Z")

</div>

Hi All,

We have 4 nodes EKS cluster. We have some pods (part of Daemonset) in pending status as the Node is full and there is no capacity in the node to run any new pod. The question is do we need to manually reshuffle the workloads to make Daemonset’s pod running in this situation or is there any configuration to overcome this issue in an automated fashion?

We come across this solution, but not sure if is there any other way to overcome this.

> **[Pod Priority and Preemption](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/)**
>
> FEATURE STATE: Kubernetes v1.14 \[stable\] Pods can have priority. Priority indicates the importance of a Pod relative to other Pods. If a Pod cannot be scheduled, the scheduler tries to preempt (evict) lower priority Pods to make scheduling of the...

Thank you in advance.

Note: we have also installed Cluster Autoscaler which works perfectly for deployments.

### Cluster information:

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