-
Notifications
You must be signed in to change notification settings - Fork 34
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
Simply mount options for uid/gid #16
Comments
Also related, evaluate fsGroupPolicy as well. |
The driver supports Delegate fsGroup to CSI Driver after the commit. This will be included in the next release. With this feature, users do not need to explicitly specify |
I haven't tested yet, but isn't this closed by release 0.1.7? |
I have a
Is there a mount option or annotation I need to provide to use this, or is it simply not rolled out to the GKE-managed version yet? |
Hi @zevisert , could you provide your cluster version? It is highly likely that the new version that includes this enhancement has not been rolled out to all the cluster versions yet. |
We're using the regular release channel default right now, so that's |
I can confirm that |
The doc is updated to describe which GKE version includes the feature: /~https://github.com/GoogleCloudPlatform/gcs-fuse-csi-driver/tree/main?tab=readme-ov-file#gke-compatibility @zevisert This feature was included in CSI version |
Right now users have to set the driver's mount options to match the uid/gid settings.
Is UID required, or is gid/fsgroup sufficient? Normally for pod volumes, having the volume ownership match the fsgroup (ie supplemental group of the contaner) is enough and uid for the volume doesn't matter.
If you enable delegate fsgroup to csidriver, then k8s will send over the fsgroup id to the NodePublishVolume call, so that could eliminate needing to repeat gid in the mount options.
The text was updated successfully, but these errors were encountered: