When the vSphere CSI driver is installed, we do not collect metrics of its CSI drivers.
Verified pass on 4.8.0-0.nightly-2021-04-19-121657 $ oc get pvc -A NAMESPACE NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE wduan-csi mypvc Bound pvc-ea0489b7-468c-41ed-8870-0534bb13159d 2Gi RWO thin-csi 9m52s wduan-intree mypvc Bound pvc-713ca14d-694c-4091-bf8a-9f1ae73a3773 2Gi RWO thin 12m TYPE kubelet_volume_stats_available_bytes gauge kubelet_volume_stats_available_bytes{namespace="wduan-csi",persistentvolumeclaim="mypvc"} 1.916198912e+09 kubelet_volume_stats_available_bytes{namespace="wduan-intree",persistentvolumeclaim="mypvc"} 2.023571456e+09
`unknown-driver` is OK. It comes from the sidecars when it calls GetPluginInfo to get the driver name. The sidecar does not know name of the driver yet at that point. Therefore it's accounted as 'unknown-driver'. You could see also other calls with `unknown-driver`, such as Probe().
Thanks, change the status to Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438