# Requesting Assistance with Node drain and pod eviction

**URL:** <https://discuss.kubernetes.io/t/requesting-assistance-with-node-drain-and-pod-eviction/24567>\
**Category:** General Discussions\
**Tags:** deployment\
**Created:** [June 20, 2023, 10:01am UTC](https://discuss.kubernetes.io/t/requesting-assistance-with-node-drain-and-pod-eviction/24567 "2023-06-20T10:01:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karan\_Kumar](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/karan_kumar/32/12749_2.png) [@Karan\_Kumar](https://discuss.kubernetes.io/u/Karan_Kumar)\
**Post date:** [June 20, 2023, 10:01am UTC](https://discuss.kubernetes.io/t/requesting-assistance-with-node-drain-and-pod-eviction/24567/1 "2023-06-20T10:01:32Z")

</div>

I have a deployment with a single replica and a pod disruption budget with minAvailable=1. When I drain the node, the pod does not evict (it is expected and needed) but the node drain process does not schedule the pod on another node. I am looking for a solution so that **when I drain the node, the pod should be first scheduled on another node, then should be evicted.**  
As such affinity is not a requirement, but increasing replica is a requirement, so I can not increase any replica.

I would greatly appreciate any guidance, best practices, or configuration recommendations from the community to achieve this desired behavior in my Kubernetes deployment.

Thank you in advance