I am trying to mount glusterfs on a kubernetes pod using a fuse mount.
Kubernetes hardcodes the backup-volfile-servers option that is giving an
error while mounting. I can mount without this option. IS there a way to
make the client happy by setting something on the server?
*Mounting arguments:
tter sysadmin plan. Users are terrible sysadmin.
> Programmers are too. Sysadmins are not very good programmers :-(
>
>
> On October 21, 2019 10:03:46 PM EDT, pankaj kumar
> wrote:
>>
>> We are attaching a gluster storage to our cluster. We give shell access
>> to
We are attaching a gluster storage to our cluster. We give shell access to
our cluster to untrusted users. Each user has a folder in gluster. The
problem is that the users could get to mount as any user id and then access
the other users files as their own. Is there a way to authenticate a user
Hi
Is it possible to not let a user with root access on the network not mount
glisterfs with any other UID than his/her own? Is there a way to
authenticate mount requests?
Thanks,
___
Gluster-users mailing list
Gluster-users@gluster.org
I am using a gluster volume share over nfs using root_squash.
I would like most of the servers in the organization use a gluster
share with their specific user id/group id and not able to read other
people's data.
But there have to be some users who can provision the root level
directory for