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
{{ message }}
This repository has been archived by the owner on Sep 7, 2022. It is now read-only.
[p0] Balu - kubernetes attempts to unmount a wrong vSphere volume and stops making any progress after that kubernetes attempts to unmount a wrong vSphere volume and stops making any progress after that kubernetes/kubernetes#37022 kubernetes attempts to unmount a wrong vSphere volume and stops making any progress after that kubernetes/kubernetes#37022
[p0] Balu - vSphere Cloud Provider triggers panic in controller-manager pod vSphere Cloud Provider triggers panic in controller-manager pod kubernetes/kubernetes#36295
[p0] Abrar - vsphere volume does not honor fsGroup vsphere volume does not honor fsGroup kubernetes/kubernetes#34039
[p0] Balu - vSphere cloudprovider does not sanitise region or failuredomain, so nodes fail to register vSphere cloudprovider does not sanitise region or failuredomain, so nodes fail to register kubernetes/kubernetes#33576
[p1] Balu - Space handling in path getDeviceNameFromMount() function doesn't return the volume path correctly when the volume path contains spaces kubernetes/kubernetes#37712. For now we can document the limitation.
[p1] Abrar - vSphere Cloud Provider: Look into the need for credentials to be stored on nodes vSphere Cloud Provider: Look into the need for credentials to be stored on nodes kubernetes/kubernetes#35339
[p2] vSphere Cloud provider: Volume detach is not issued when VM is not present vSphere Cloud provider: Volume detach is not issued when VM is not present kubernetes/kubernetes#33061
The text was updated successfully, but these errors were encountered: