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
A default deployment of cinder CSI results in constant errors in logs:
csi-snapshotter W0210 21:36:23.865665 1 reflector.go:424] github.com/kubernetes-csi/external-snapshotter/client/v6/informers/externalversions/factory.go:117: failed to
list *v1.VolumeSnapshotContent: the server could not find the requested resource (get volumesnapshotcontents.snapshot.storage.k8s.io)
csi-snapshotter E0210 21:36:23.865719 1 reflector.go:140] github.com/kubernetes-csi/external-snapshotter/client/v6/informers/externalversions/factory.go:117: Failed to
watch *v1.VolumeSnapshotContent: failed to list *v1.VolumeSnapshotContent: the server could not find the requested resource (get volumesnapshotcontents.snapshot.storage.k8s
.io)
IIUC, some other component (CRDs and/or https://github.com/kubernetes-csi/external-snapshotter ?) need to be installed for this to work.
If the cinder-CSI chart does not install them by default, shouldn't the csi-snapshotter container be disabled by default (via helm value) to avoid wasting resources and producing spurious errors?
The text was updated successfully, but these errors were encountered:
A default deployment of cinder CSI results in constant errors in logs:
IIUC, some other component (CRDs and/or https://github.com/kubernetes-csi/external-snapshotter ?) need to be installed for this to work.
If the cinder-CSI chart does not install them by default, shouldn't the csi-snapshotter container be disabled by default (via helm value) to avoid wasting resources and producing spurious errors?
The text was updated successfully, but these errors were encountered: