Bobcares

Kubectl Remove Pending Pod | Top Tips

by | Jun 28, 2022

Kubectl remove pending pod like a pro with a little help from our experts. Read on to find out more. 

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Services.

Let’s take a look at how our Support Team helped our customers with removing pending pods via kubectl and other ways.

Tutorial to Remove Pending Pod Kubectl

We can remove all the pods from a node or a specific one from our cluster without too much trouble. To begin with, our Support Team recommends confirming the name of the node we want to remove with the following command:

kubectl get nodes
kubectl get pods -o wide | grep

This gives us a peek at all the pods to ensure we can remove the nods on the pods safely.

After that we have to use the following command to evict the user pods from the node:

kubectl drain

These user pods will get scheduled to other nodes by the controller. Furthermore, we can run several drain commands in different shells in order to drain multiple nodes. However, it executes only one at a time.

Then, we can ensure there are no more user pods on the node via this command:

get pods

In some scenarios, there may still be system pods running on the node. Moreover, there might also be DaemonSet pods on the node. In case the drain command fails, it is because a controller is not managing some of the pods. We can resolve this by running the drain once again with the –force flag. This deletes all the pods.

Kubectl Remove Pending Pod

Now, we can either replace the node or troubleshoot it. If we opt for the former, we have to use the following command to delete the node initially:

kubectl delete node

Then, we can replace it with a new node. However, if our nodes are in an Amazon AutoScaling Group, we can terminate the EC2 instance backing our node and have it replaced within a few minutes.

Troubleshooting tips to remove pending pods

If the above procedure did not help remove the pods in your node, here are a few troubleshooting tips via our Support Team:

  • Try deleting the statefulset that controls the pods before deleting the pods directly.
    kubectl delete statefulset
  • The following command may come in handy to delete pods:
    kubectl delete pod  --grace-period=0 --force -n kube-system
  • Alternatively, remove pending pod by deleting the deployment file with kubectl command:
    kubectl delete -f deployment-file-name.yaml
  • If another pod gets recreated automatically after deleting it as per the number of replicas we mentioned during cluster creation, we have to use this command:
    $ ./cluster/kubectl.sh delete pod

Let us know in the comments which method helped remove pending pods.

[Need assistance with a different issue? We are available 24/7.]

Conclusion

At the end of the day, we went through different ways to remove pending pods in our node. Our skilled Support Engineers at Bobcares also took us through some additional troubleshooting tips to help get the job done.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF