harvester-csi-driver-lvm: grant snapshot location ConfigMap permissions

[WebberHuang1118]

Problem

The LVM CSI driver now persists each snapshot's node and volume-group location in a namespaced ConfigMap. The packaged Harvester LVM CSI chart does not grant the harvester-csi-driver-lvm service account permission to manage those location records, so snapshot creation and annotation-free pre-existing snapshot deletion cannot use the registry.

Solution

Add a namespace-scoped Role and RoleBinding to charts/harvester-csi-driver-lvm, granting its existing service account only get, create, and delete access to ConfigMaps.

Impact

The packaged LVM driver can create, resolve, and remove per-snapshot location records without receiving cluster-wide ConfigMap permissions. The generic harvester-csi-driver chart is unchanged.

Validation

• helm lint charts/harvester-csi-driver-lvm
• helm template harvester-csi-driver-lvm charts/harvester-csi-driver-lvm --namespace harvester-system
• helm lint charts/harvester-csi-driver
• helm template harvester-csi-driver charts/harvester-csi-driver --namespace kube-system
• git diff --check

Related to harvester/harvester#11339.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request