John Strunk

This is not a priority for GCS 1.0.

This seems related, but not consistent with the `fsGroup` parameter in a container or pod's `securityContext`. The info on fsGroup points to https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/volume-ownership-management.md Also related in the volume design that...

Related Heketi items: - Be able to assign a gid to a volume as it's created: https://github.com/heketi/heketi/pull/530 - BZ for ^^^ https://bugzilla.redhat.com/show_bug.cgi?id=1356437 - Enable sgid on the volume: https://github.com/heketi/heketi/issues/611

Thanks to @rootfs I believe we have the source: - The bug: https://github.com/openshift/origin/issues/11556 - The patch & related discussion on assigning gids: https://github.com/kubernetes/kubernetes/pull/35460

Could you clarify why is this a priority? We only have a handful of (very busy) folks involved in the project. GitHub built in mechanisms seem sufficient at this stage.

I read your request to Nigel as urgent. Looks like we are agreed this is a low priority item.

Using the GCS deployment scripts is good, and we may want to wait on this issue until they get committed to gluster/gcs and just use them from there. My current...

The PR for GCS environment is up: https://github.com/gluster/gcs/pull/6 Let's see what we can do to get that merged and build on top.

I don't have the actual SC to give you at this point. It's a placeholder so we don't forget about it. The idea is that we work w/ perf team...

@BoboTiG, thanks for distilling that solution. I'm fine w/ closing the issue. If I run into problems making the change, I'll re-open for further discussion.