Hi,

The chart actually fixe the arg "--v=5" which but all logs into trace level.
This generate a lot of logs.

Could you please templating the loglevel "--v={{ .LogLevel }}" ?

It is ever done into the rook project: see rook/rook@88b5d5e

Regards

Line 107 of values.yaml for version 2.0.0 of the RBD chart (which specifies the tag for the cephcsi image) refers to "2.0.0", which I believe should be "v2.0.0".

This will cause all installations to fail, AFAIK.

There is only one csi-snapshotter in helm charts and it can only reconcile the volumeSnapshotContent and it nearly useless.

as the design of snapshotter

Both the snapshot controller and CSI external-snapshotter sidecar follow controller pattern and uses informers to watch for events. The snapshot controller watches for VolumeSnapshot and VolumeSnapshotContent create/update/delete events.

The CSI external-snapshotter sidecar only watches for VolumeSnapshotContent create/update/delete events. It filters out these objects with Driver== specified in the associated VolumeSnapshotClass object and then processes these events in workqueues with exponential backoff.

The CSI external-snapshotter sidecar talks to CSI over socket (/run/csi/socket by default, configurable by -csi-address).

after a certain version(I don't know it clearly), external-snapshotter split cmd/csi-snapshotter intocmd/csi-snapshotter and cmd/snapshot-controller

So shall we add one more container for snapshot-controller? or we have other considerations for not doing this.