Skip to content
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

New csiplugin-configmap.yaml setting to override PVs's volumeAttributes.mounter #4700

Closed
FredNass opened this issue Jul 3, 2024 · 4 comments
Labels
wontfix This will not be worked on

Comments

@FredNass
Copy link

FredNass commented Jul 3, 2024

Describe the feature you'd like to have

I'd like to be able to set the plugin mounter type globally (fuse or kernel) so that all PVs in a cluster are mounted the same way, regardless of each PV's volumeAttributes.mounter set by SC at creation time.

What is the value to the end user? (why is it a priority?)

Over time, we had to change SC's mounter type to fuse due to kernel lock issues when using MDS's balancer in active/active mode. We now have some PV's with volumeAttributes.mounter: fuse and other PVs with volumeAttributes.mounter: kernel in the same cluster, which results in some PVs being mounted with ceph-fuse and other PVs being mounted with kernel in the same cluster.

This new setting would allow users to choose the mounter type they want to use globally for all PVs and ensure all PVs use the same mounter, without having to change each PV's volumeAttributes.mounter which is currently not possible since volumeAttributes.mounter is immutable (see #4691).

How will we know we have a good solution? (acceptance criteria)

PVs would all be mounted using the same client, whatever they have for volumeAttributes.mounter.

@FredNass
Copy link
Author

FredNass commented Jul 16, 2024

In case anyone needs to convert Cephfs PVC (RWO vs RWX) and/or Cephfs PV (fuse vs kernel), you can use this script: https://github.com/FredNass/k8s_tools/blob/main/conversion_pvc_cephfs.sh

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the wontfix This will not be worked on label Aug 15, 2024
@Madhu-1 Madhu-1 removed the wontfix This will not be worked on label Aug 16, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the wontfix This will not be worked on label Sep 15, 2024
Copy link

This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants