search

kvaps / kubectl-node-shell

Exec into node via kubectl
Apache License 2.0
1.48k stars 178 forks source link

node-shell pod timing out #53

Open rwagner3 opened 1 year ago

rwagner3 commented 1 year ago

I'm seeing the node-shell pod timing out and getting deleted. I do not see a reason why it should timeout, other than perhaps the node is busy. Nothing in kubectl events other than it getting killed after some time. Is it possible to increase the timeout before it gets deleted?

$ kubectl node-shell aks-servpool1-14120502-vmss000017 spawning "nsenter-j7g30x" on "aks-servpool1-14120502-vmss000017" error: timed out waiting for the condition pod "nsenter-j7g30x" deleted

$ ke | grep nsenter-j7g30x 19s Normal Pulling pod/nsenter-j7g30x Pulling image "docker.io/library/alpine" 19s Normal Pulled pod/nsenter-j7g30x Successfully pulled image "docker.io/library/alpine" in 264.806927ms (264.815427ms including waiting) 19s Normal Created pod/nsenter-j7g30x Created container nsenter 19s Normal Started pod/nsenter-j7g30x Started container nsenter 18s Normal Killing pod/nsenter-j7g30x Stopping container nsenter

pycgo commented 10 months ago

I encountered this situation in the K8S 1.28 version and couldn't even connect to the lower version 1.27 1.26 without any problem. Can you check if the version is incompatible? I am using the latest master minute

pycgo commented 10 months ago

I know the reason now, and after 1.28 use crio-1.28, it no longer supports cgoup1 to allocate CPUs, In order to be compatible, we should remove the CPU restrictions in the script, and then I successfully connected to the node on my end。