-
Notifications
You must be signed in to change notification settings - Fork 22
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
-o mfspassword in the CSI #12
Comments
Hi, Thank you for bringing it to our attention. |
Hi, I would like to inform that I have added an additional argument to the driver, which helps to pass an additional mfsmount option to the driver. Also I would like to add that I have build dev container image so image and arguments now should look like this:
Configuration example is available here: If everything works without issues, I will create a pull request. |
Were you able to get the passwords -o mfspasswords to work with moosefs-csi? Thanks |
@dretechtips yes. As I said in my previous response. I have added one extra argument to moosefs-csi to pass additional options during mfsmount process. Please check this example: |
@xandrus et. al, I am getting the following error using the 0.9.6-dev moosefs-csi-plugin in Ubuntu Jammy container from my PVC mounted pods using k3s distribution of Kubernetes (v1.26+).
when deploying the these test case yaml files.
Kubernetes Node Setup: 5x Raspberry PI (arm64) & 1x Generic Server (amd64). MooseFS Storage Setup: 5x Generic Servers (amd64) MooseFS mfsexports.cfg Configuration
An overall summary of the Kubernetes deployment is that I using the @Kunde21 csi resizer, attacher, etc. (not moosefs-csi-plugin) from the master branch None of my pods are crashing. Node pod logs
However, I find it odd that the Controller Node keeps alternating between Published and Unpublished Volume state.
There is a lack of information over the internet over the latest development builds of moosefs-csi-plugin for debugging. Try running a bare metal instance of moosefs-csi-plugin w/ multi-architecture (arm64/amd64). And tell me if you guys were able to successfully get PVC mounting to work using k3s or any other Kubernetes forks. Thanks, EDIT: It was an issue w/ my RBAC configuration & symlinks. |
mfsmount
allows the user to specify the following option to mount to a MooseFS master server that requires password authentication to view a specific directory.This is useful in a production environment where certain directories on the Master server need to be restricted from the clients. I am just wondering whether such a feature exist on moosefs-csi?
The text was updated successfully, but these errors were encountered: