<p>I'm running into an issue managing my Kubernetes pods.</p>

<p>I had a deploy instance which I removed and created a new one. The pod tied to that deploy instance shut down as expected and a new one came up when I created a new deploy, as expected.</p>

<p>However, once I changed the deploy, a second pod began running. I tried to "kubectl delete pod pod-id" but it would just recreate itself again. </p>

<p>I went through the same process again and now I'm stuck with 3 pods, and no deploy. I removed the deploy completely, and I try to delete the pods but they keep recreating themselves. This is an issue because I am exhausting the resources available on my Kubernetes. </p>

<p>Does anyone know how to force remove these pods? I do not know how they are recreating themselves if there's no deploy to go by.</p>

BURGERFLIPPER101
<p>I've had this happen after issuing a <code>rollout restart deployment</code> while a pod was already in an error or creating state, and explicitly deleting the second pod only resulted in a new one getting scheduled (trick birthday candle situation).</p>
<p>I find almost any time I have an issue like this it can be fixed by simply zeroing out the <code>replicaSets</code> in the deployment, applying, then restoring <code>replicaSets</code> to the original value.</p>
