How to Delete all Pods in a ReplicaSet
ReplicaSet keeps a constant number of pods running. Learn how to delete pods quickly without complicated commands imperatively!
I recently got into the Cloud Native Foundations Scholarship Program by Udacity, and with that, my day-to-day interaction with Kubernetes has increased. The exposure is good because I am learning Kubernetes and patching problems and sharing some tricks to solve my problems here.
One of them is to delete all pods in a ReplicaSet. I went through many StackOverflow questions with one-line finalizers that would do the job instantly, but it was all trial and error with 20 commands to find the one. In addition to that, pasting random finalizers that you don’t understand on the terminal is not recommended. Also, even if I am a massive fan of Googling stuff out, I get tired of Googling the same queries 10 times.
Delete All Pods in ReplicaSet (My Approach)
The purpose of a ReplicaSet is to keep a consistent number of Pods always running. As a result, you can scale the number of pods (declaratively/imperatively) to anything that your server can manage.
Theoretically, you can scale your ReplicaSet to zero pods, and that’s what I did using the subcommand scale by scaling the number of pods to 0 on the ReplicaSet.
The following imperative command helped me remove all the pods in a ReplicaSet without deleting the ReplicaSet.
kubectl scale rs/new-replica-set --replicas=0
new-replica-set would be replaced by the ReplicaSet whose pods you want to delete. You can deploy new pods via the ReplicaSet using the above command with the value in --replicas as your desired number of pods or via declarative way using kubectl edit replicaset new-replica-set.
Delete ReplicaSet + Pods
This is a standard and straightforward approach if you want to delete the ReplicaSet as well as the pods together by using subcommand delete with new-replica-set replaced with the name of the ReplicaSet you want to delete.
kubectl delete rs new-replica-setHappy Learning!
Published at DZone with permission of Hrittik Roy. See the original article here.
Opinions expressed by DZone contributors are their own.