kubernetes: No timeout when Kubelet Calling cni plugin
BUG REPORT:
/kind bug
What happened: When the kubelet create sandbox by cni plugin. It will just use exec.Cmd to call the cni binary file. In some cni plugin,such as contiv,the cni binary file may be locked and no return. In this case, when kubelet first time call RunPodSandbox got a ctx timeout. the next time kubelet re-creates PodSandbox, it will always report this timeout.
What you expected to happen: Next time kubelet re-creates PodSandbox it will do call cni again.
How to reproduce it (as minimally and precisely as possible): Create a pod in a node,and make the cni binary file not return.
Environment:
- Kubernetes version (use
kubectl version):v.1.9.2
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 29 (20 by maintainers)
@nikopen yes, i just waiting for the cni plugin release a new version.Then i will upgrade our kubelet’s dockeshim to use the new cni plugin.
@nikopen Yes,kubelet should update the cni version. I will change the kubelet when the cni project release a new version
we are also got affected by this issue https://github.com/kubernetes/kubernetes/issues/45419, can someone take a look at this PR. we will be happy to test this out
/assign liucimin