Score:0

Kubernetes - Unable to cordon the node

cn flag

We have on-prem cluster. I am trying to cordon a node using kubectl cordon <node> the command is successful, but when I am running command kubectl get nodes I see nodes is still ready. Where should I check next?

I didnt find any error in api-server. Where should I check? Etcd logs (how to check them) ? Scheduler?

Score:0
et flag

It is possible that you still have some daemonsets on your node that are preventing the node from being cordoned off. As per the guide on Kubernetes.io, try the following:

kubectl drain --ignore-daemonsets <node name>

Once this has completed, you can safely power off the node. Once it comes back up, you can bring it back into the fold with:

kubectl uncordon <node name>

Let me know if that helps.

#kubernetes #drain #cordon

tollboy avatar
cn flag
Hello @XanderS This is not about draining but cordoning, drain empty the node of any pods. Cordoning only tell scheduler to stop scheduling further workloads to cordoned node.
XanderS avatar
et flag
I realise that it is not the same, but I was offering a solution to the possible issue that may be causing the cordoning not to work as designed.
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.