Pods stuck in terminating state after deleting ReplicationController

0 votes

I deleted a replication controller with about 10 pods and after checking with kubectl get pods I can see that some of the pods are staying in terminating status. I've got one master and three nodes in my cluster. Why is this happening?

NAME        READY     STATUS        RESTARTS   AGE
pod-186o2   1/1       Terminating   0          2h
pod-4b6qc   1/1       Terminating   0          2h
pod-8xl86   1/1       Terminating   0          1h
pod-d6htc   1/1       Terminating   0          1h
pod-vlzov   1/1       Terminating   0          1h
Jan 4 in Kubernetes by shubham
• 6,890 points
325 views

1 answer to this question.

0 votes

Delete the pods by FORCE, You should.<(-.-)>

kubectl delete pod NAME --grace-period=0 --force
answered Jan 4 by ajs3033
• 7,280 points

Related Questions In Kubernetes

0 votes
1 answer

Pods stuck in CrashBackLoopOff state

There are three possibilities here @Ali, Check your ...READ MORE

answered Jan 4 in Kubernetes by Lissa
69 views
+2 votes
2 answers

Kubernetes Pods in Pending State

Hey @Shyam, you get this error because ...READ MORE

answered Oct 31, 2018 in Kubernetes by Kalgi
• 40,420 points
1,868 views
0 votes
1 answer

deleting pods using kubernetes replication controller

The pods which are managed by ReplicationController ...READ MORE

answered Jul 24, 2018 in Kubernetes by DareDev
• 6,810 points
210 views
0 votes
1 answer
0 votes
1 answer
0 votes
3 answers

Error while joining cluster with node

Hi Kalgi after following above steps it ...READ MORE

answered Jan 17 in Others by anonymous
2,089 views
+3 votes
1 answer
0 votes
1 answer
0 votes
1 answer

No pods created after launching a DaemonSet

Kubelet service restart won't help you with ...READ MORE

answered Dec 28, 2018 in Kubernetes by ajs3033
• 7,280 points
240 views