When the plugin cannot pull the image (in my case egress policy was at fault), and maybe in other cases where the pod is not starting, the kubectl just hangs without information that it's waiting or something, no timeout and does not even respond to Ctrl+C for some reason.
Expected behaviour:
- print a message that is waiting for the pod to start (after e.g. 10 sec)
- timeout and abort after e.g. 5 minutes at most
- maybe recreate the pod like 3 times before giving up
- respond to
Ctrl+C
When the plugin cannot pull the image (in my case egress policy was at fault), and maybe in other cases where the pod is not starting, the
kubectljust hangs without information that it's waiting or something, no timeout and does not even respond toCtrl+Cfor some reason.Expected behaviour:
Ctrl+C