You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We advertise VOLUME_MOUNT_GROUP capability, so NodePublishVolume.volume_capability.volume_mount_group is set to securityContext.fsGroup. Problem is, we only change gid of the files, but accourding to spec we also need to pass gid to the mount command and give group members rw access
// If SP has VOLUME_MOUNT_GROUP node capability and CO provides
// this field then SP MUST ensure that the volume_mount_group
// parameter is passed as the group identifier to the underlying
// operating system mount system call, with the understanding
// that the set of available mount call parameters and/or
// mount implementations may vary across operating systems.
// Additionally, new file and/or directory entries written to
// the underlying filesystem SHOULD be permission-labeled in such a
// manner, unless otherwise modified by a workload, that they are
// both readable and writable by said mount group identifier.
// This is an OPTIONAL field.
string volume_mount_group = 3;
The text was updated successfully, but these errors were encountered:
We advertise
VOLUME_MOUNT_GROUP
capability, soNodePublishVolume.volume_capability.volume_mount_group
is set tosecurityContext.fsGroup
. Problem is, we only change gid of the files, but accourding to spec we also need to pass gid to the mount command and give group members rw accessThe text was updated successfully, but these errors were encountered: