<p>I am wondering if Kubernetes can automatically move the pods to another node if that node resources are on critical, or if that happens only for pods managed by Replica Sets?</p>
<p>In particular:</p>
<ol>
<li>What happens when a <strong>bare pod</strong> (not managed by Replica Sets or similar) is evicted? Is it moved to another node or it is just removed?</li>
<li>In case it is &quot;moved&quot; to a new node, is it really moved or it is recreated? For example, does its <em>age</em> change?</li>
<li>Is it true that only <strong>pods managed by Deployments and Replica Sets</strong> are moved/recreated on a new node while bare pods are simply removed in case of resource shortage?</li>
</ol>

collimarco
<blockquote>
<ol>
<li>What happens when a  <strong>bare pod</strong>  (not managed by Replica Sets or similar) is evicted? Is it moved to another node or it is just removed?</li>
</ol>
</blockquote>
<p>Pod is <a href="https://kubernetes.io/docs/concepts/workloads/pods/#working-with-pods" rel="nofollow noreferrer">designed as a relatively ephemeral, disposable entity</a>; when it is evicted, it's deleted by a Kubelet agent running on the node. There is no recreating / moving to the other node, it's just removed (for bare pods). The controllers (like Deployment, StatefulSet, DaemonSet) are responsible for <a href="https://kubernetes.io/docs/concepts/workloads/pods/#pods-and-controllers" rel="nofollow noreferrer">placing the replacement pods</a>.</p>
<blockquote>
<ol start="2">
<li>In case it is &quot;moved&quot; to a new node, is it really moved or it is recreated? For example, does its  <em>age</em>  change?</li>
</ol>
</blockquote>
<p>As I mentioned in the answer from the previous question, in the Kubernetes architecture pods are <a href="https://kubernetes.io/docs/concepts/workloads/pods/#working-with-pods" rel="nofollow noreferrer">designed as relatively ephemeral, disposable entities</a>, so there is no &quot;moving&quot;. It's recreated as a &quot;fresh&quot; pod on the same or new node. The <em>age</em> parameter is changed, it's starting counting from the beginning as it is a new pod.</p>
<blockquote>
<ol start="3">
<li>Is it true that only  <strong>pods managed by Deployments and Replica Sets</strong>  are moved/recreated on a new node while bare pods are simply removed in case of resource shortage?</li>
</ol>
</blockquote>
<p>Not only pods managed by Deployment/ReplicaSets but it's also true for some <a href="https://kubernetes.io/docs/concepts/workloads/controllers/" rel="nofollow noreferrer">other controllers</a> (e.g StatefulSet). When a pod is missing (it's got evicted by resource shortage or there is a rolling update), the <a href="https://kubernetes.io/docs/concepts/workloads/controllers/" rel="nofollow noreferrer">controllers</a> are  making requests to the <a href="https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/" rel="nofollow noreferrer">Kubernetes Scheduler</a> to roll-out new pods. The bare pods, as answered in the first question, are not  recreated.</p>
<p>If you want to read more about this process, check <a href="https://stackoverflow.com/questions/69976108/kubernetes-control-plane-communication/70007320#70007320">my other answer</a>.</p>
