search

kubernetes / examples

Kubernetes application example tutorials
Apache License 2.0
6.21k stars 4.54k forks source link

cephfs subvolume uid, gid information not retain after mounting the subvolumegroup #474

Closed zeddit closed 9 months ago

zeddit commented 1 year ago

I created a subvolumegroup with default settings as:

ceph fs subvolume create myfs mysvg

then I add some subvolumes under the subvolumegroup with uid,gid settings, like:

ceph fs subvolume create myfs user1 --size 10737418240 --group_name mysvg --uid 190002 --gid 19001 --mode 640 --namespace-isolated

then I try to mount the subvolumegroup from host os and k8s pod like:

sudo mount -t ceph -o mds_namespace=myfs,name=user1,secret=AQA9CxBkqx+CAhABF2Gu+f7vybws6HkAO2KKYg== 10.0.26.1:6789:/volumes/mysvg /mnt

and 

   - name: cephfs
        cephfs:
          monitors:
            - 10.0.26.1:6789
            - 10.0.26.2:6789
            - 10.0.26.3:6789
          user: user1
          secretRef:
            name: rook-ceph-client-aitopia
          path: "/volumes/mysvg"

However, all subvolumes have user and group as root and root, where I expect should be the uid and gid I have set. Is there any configuration that I missed, I can find few documentations about this topic.

Great thanks.

zeddit commented 1 year ago

I have checked the uid and gid of subvolumes with ceph fs subvolume info and the results show that the uid and gid was set correctly. However, after mount, these identity information lost.

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 9 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 9 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/examples/issues/474#issuecomment-1900855412): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.