failed to list *v1.VolumeSnapshotContent: the server could not find the requested resource (get volumesnapshotcontents.snapshot.storage.k8s.io)

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?

Start by inspecting the cinder CSI Helm chart's default values and the csi-snapshotter container configuration, then check whether the required snapshot CRDs or external-snapshotter are installed. Confirm the default deployment no longer produces the reported missing-resource errors, either by disabling the container when dependencies are absent or by ensuring those dependencies are provided.