You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
klog.Fatalf("restarting pod because received event %v\n", event)
stopCh<-struct{}{}
What did you expect to happen?
The pod should not exit at klog.Fatalf and allow the signal to be send to the channel
How 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
$ kubectl version
# paste output here
v1.31.0
Cloud provider or hardware configuration
OS version
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
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:
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: