cloud provider vsphere pod didn't restart gracefully as expected #1212
Labels
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
What happened?
In https://github.com/kubernetes/cloud-provider-vsphere/blob/master/cmd/vsphere-cloud-controller-manager/main.go#L273, cloud provider vsphere is using
klog.Fatalf
to log information, it will exit directly so the stop channel didn't receive the signalWhat did you expect to happen?
The pod should not exit at
klog.Fatalf
and allow the signal to be send to the channelHow can we reproduce it (as minimally and precisely as possible)?
existing in current version
Anything else we need to know (please consider providing level 4 or above logs of CPI)?
No response
Kubernetes version
Cloud provider or hardware configuration
OS version
Kernel (e.g.
uname -a
)Install tools
Container runtime (CRI) and and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
Others
The text was updated successfully, but these errors were encountered: