Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

helm chart volumesnapshot rbac problem #623

Closed
akirose opened this issue Mar 5, 2024 · 1 comment · Fixed by #628 or #629
Closed

helm chart volumesnapshot rbac problem #623

akirose opened this issue Mar 5, 2024 · 1 comment · Fixed by #628 or #629

Comments

@akirose
Copy link

akirose commented Mar 5, 2024

What happened:
It seems there is an issue with the RBAC configuration in the Helm chart. The csi-nfs-controller always includes the csi-snapshotter container. However, the csi-snapshotter container requires permissions for volumesnapshotcontents.snapshot.storage.k8s.io, but in the Helm chart, these permissions are only applied if the externalSnapshotter.enabled value in the Values is set to true.

What you expected to happen:
If the functionality is not intended to be used, the csi-snapshotter container should be excluded, and the related RBAC should not be applied. There should be a configuration option in the Values to handle this scenario.

How to reproduce it:
To install the chart with this setting, set the externalSnapshotter.enabled value to false.

Anything else we need to know?:

Environment:

  • CSI Driver version: 4.6.0
  • Kubernetes version (use kubectl version): 1.28.3
  • OS (e.g. from /etc/os-release): Ubuntu 22.04
  • Kernel (e.g. uname -a):
  • Install tools: helm
  • Others:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant