Kubernetes pod gets recreated when deleted

Question

I have started pods with command    kubectl run busybox --image busybox --restart Never --tty -i --generator run-pod v1   Something went wrong  and now I can t delete this Pod   I tried using the methods described below but the Pod keeps being recreated     kubectl delete pods  busybox-na3tm pod  busybox-na3tm  deleted   kubectl get pods NAME                                     READY     STATUS              RESTARTS   AGE busybox-vlzh3                            0 1       ContainerCreating   0          14s    kubectl delete pod busybox-vlzh3 --grace-period 0     kubectl delete pods --all pod  busybox-131cq  deleted pod  busybox-136x9  deleted pod  busybox-13f8a  deleted pod  busybox-13svg  deleted pod  busybox-1465m  deleted pod  busybox-14uz1  deleted pod  busybox-15raj  deleted pod  busybox-160to  deleted pod  busybox-16191  deleted     kubectl get pods --all-namespaces NAMESPACE   NAME            READY     STATUS              RESTARTS   AGE default     busybox-c9rnx   0 1       RunContainerError   0          23s

User · Answer

When the pod is recreating automatically even after the deletion of the pod manually, then those pods have been created using the Deployment. When you create a deployment, it automatically creates ReplicaSet and Pods. Depending upon how many replicas of your pod you mentioned in the deployment script, it will create those number of pods initially. When you try to delete any pod manually, it will automatically create those pod again.

Yes, sometimes you need to delete the pods with force. But in this case force command doesn’t work.

User · Answer

I also faced the issue  I have used below command to delete deployment   kubectl delete deployments DEPLOYMENT NAME   but still pods was recreating  So I crossed check the Replica Set by using below command  kubectl get rs   then edit the replicaset to 1 to 0  kubectl edit rs REPICASET NAME

User · Answer

The root cause for the question asked was the deployment job replicasets spec attribute strategy- gt type which defines what should happen when the pod will be destroyed  either implicitly or explicitly   In my case  it was Recreate   As per  nomad s answer  deleting the deployment job replicasets is the simple fix to avoid experimenting with deadly combos before messing up the cluster as a novice user   Try the following commands to understand the behind the scene actions before jumping into debugging    kubectl get all -A -o name kubectl get events -A   grep  lt pod-name gt

User · Answer

Many answers here tells to delete a specific k8s object  but you can delete multiple objects at once  instead of one by one    kubectl delete deployments jobs services pods --all -n  lt namespace gt   In my case  I m running OpenShift cluster with OLM - Operator Lifecycle Manager  OLM is the one who controls the deployment  so when I deleted the deployment  it was not sufficient to stop the pods from restarting    Only when I deleted OLM and its subscription  the deployment  services and pods were gone   First list all k8s objects in your namespace      kubectl get all -n openshift-submariner  NAME                                       READY   STATUS    RESTARTS   AGE pod submariner-operator-847f545595-jwv27   1 1     Running   0          8d   NAME                                  TYPE        CLUSTER-IP       EXTERNAL-IP   PORT S     AGE service submariner-operator-metrics   ClusterIP   101 34 190 249    lt none gt         8383 TCP   8d NAME                                  READY   UP-TO-DATE   AVAILABLE   AGE deployment apps submariner-operator   1 1     1            1           8d NAME                                             DESIRED   CURRENT   READY   AGE replicaset apps submariner-operator-847f545595   1         1         1       8d   OLM is not listed with get all  so I search for it specifically     kubectl get olm -n openshift-submariner  NAME                                                      AGE operatorgroup operators coreos com openshift-submariner   8d NAME                                                             DISPLAY      VERSION clusterserviceversion operators coreos com submariner-operator   Submariner   0 0 1    Now delete all objects  including OLMs  subscriptions  deployments  replica-sets  etc     kubectl delete olm svc rs rc subs deploy jobs pods --all -n openshift-submariner  operatorgroup operators coreos com  openshift-submariner  deleted clusterserviceversion operators coreos com  submariner-operator  deleted deployment extensions  submariner-operator  deleted subscription operators coreos com  submariner  deleted service  submariner-operator-metrics  deleted replicaset extensions  submariner-operator-847f545595  deleted pod  submariner-operator-847f545595-jwv27  deleted   List objects again - all gone     kubectl get all -n openshift-submariner No resources found     kubectl get olm -n openshift-submariner No resources found

User · Answer

In my case I deployed via a YAML file like kubectl apply -f deployment yaml and the solution appears to be to delete via kubectl delete -f deployment yaml

User · Answer

Instead of removing NS you can try removing replicaSet  kubectl get rs --all-namespaces   Then delete the replicaSet   kubectl delete rs your app name

User · Answer

If you have a job that continues running  you need to search the job and delete it   kubectl get job --all-namespaces   grep  lt name gt   and  kubectl delete job  lt job-name gt

User · Answer

This will provide information about all the pods deployments  services and jobs in the namespace   kubectl get pods services  deployments  jobs   pods can either be created by deployments or jobs  kubectl delete job  job name  kubectl delete deployment  deployment name    If you delete the deployment or job then restart of the pods can be stopped

User · Answer

if your pod has name like name-xxx-yyy  it could be controlled by a replicasets apps named name-xxx  you should delete that replicaset first before deleting the pod  kubectl delete replicasets apps name-xxx

User · Answer

Instead of trying to figure out whether it is a deployment  deamonset  statefulset    or what  in my case it was a replication controller that kept spanning new pods    In order to determine what it was that kept spanning up the image I got all the resources with this command   kubectl get all  Of course you could also get all resources from all namespaces   kubectl get all --all-namespaces  or define the namespace you would like to inspect   kubectl get all -n NAMESPACE NAME  Once I saw that the replication controller was responsible for my trouble I deleted it   kubectl delete replicationcontroller CONTROLLER NAME

User · Answer

You can do kubectl get replicasets check for old deployment based on age or time  Delete old deployment based on time if you want to delete same current running pod of application  kubectl delete replicasets  lt Name of replicaset gt

User · Answer

After taking an interactive tutorial I ended up with a bunch of pods  services  deployments   me pooh    gt  kubectl get pods services NAME                                       READY   STATUS    RESTARTS   AGE pod kubernetes-bootcamp-5c69669756-lzft5   1 1     Running   0          43s pod kubernetes-bootcamp-5c69669756-n947m   1 1     Running   0          43s pod kubernetes-bootcamp-5c69669756-s2jhl   1 1     Running   0          43s pod kubernetes-bootcamp-5c69669756-v8vd4   1 1     Running   0          43s  NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT S    AGE service kubernetes   ClusterIP   10 96 0 1     lt none gt         443 TCP   37s me pooh    gt  kubectl get deployments --all-namespaces NAMESPACE     NAME                  DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE default       kubernetes-bootcamp   4         4         4            4           1h docker        compose               1         1         1            1           1d docker        compose-api           1         1         1            1           1d kube-system   kube-dns              1         1         1            1           1d   To clean up everything  delete --all worked fine   me pooh    gt  kubectl delete pods services deployments --all pod  kubernetes-bootcamp-5c69669756-lzft5  deleted pod  kubernetes-bootcamp-5c69669756-n947m  deleted pod  kubernetes-bootcamp-5c69669756-s2jhl  deleted pod  kubernetes-bootcamp-5c69669756-v8vd4  deleted service  kubernetes  deleted deployment extensions  kubernetes-bootcamp  deleted   That left me with  what I think is  an empty Kubernetes cluster   me pooh    gt  kubectl get pods services deployments NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT S    AGE service kubernetes   ClusterIP   10 96 0 1     lt none gt         443 TCP   8m

User · Answer

You need to delete the deployment  which should in turn delete the pods and the replica sets https   github com kubernetes kubernetes issues 24137  To list all deployments   kubectl get deployments --all-namespaces   Then to delete the deployment   kubectl delete -n NAMESPACE deployment DEPLOYMENT   Where NAMESPACE is the namespace it s in  and DEPLOYMENT is the name of the deployment   In some cases it could also be running due to a job or daemonset  Check the following and run their appropriate delete command   kubectl get jobs  kubectl get daemonsets app --all-namespaces  kubectl get daemonsets extensions --all-namespaces

User · Answer

I experienced a similar problem  after deleting the deployment  kubectl delete deploy  lt name gt    the pods kept  Running  and where automatically re-created after deletion  kubectl delete po  lt name gt     It turned out that the associated replica set was not deleted automatically for some reason  and after deleting that  kubectl delete rs  lt name gt    it was possible to delete the pods

User · Answer

In some cases the pods will still not go away even when deleting the deployment  In that case to force delete them you can run the below command   kubectl delete pods podname --grace-period 0 --force

User · Answer

Look out for stateful sets as well   kubectl get sts --all-namespaces   to delete all the stateful sets in a namespace      kubectl --namespace  lt yournamespace gt  delete sts --all   to delete them one by one  kubectl --namespace ag1 delete sts mssql1  kubectl --namespace ag1 delete sts mssql2 kubectl --namespace ag1 delete sts mssql3

User · Answer

With deployments that have stateful sets  or services  jobs  etc   you can use this command  This command terminates anything that runs in the specified  lt NAMESPACE gt  kubectl -n  lt NAMESPACE gt  delete replicasets deployments jobs service pods statefulsets --all  And forceful kubectl -n  lt NAMESPACE gt  delete replicasets deployments jobs service pods statefulsets --all --cascade true --grace-period 0 --force

[kubernetes] Kubernetes pod gets recreated when deleted

Examples related to kubernetes

Examples related to kubectl