-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Add NFS as a storage backend #1551
Comments
NFS already works fine as volumes in kubernetes. What would be the advantage of doing this with rook? |
@dimm0 my understanding with NFS in Kubernetes from https://kubernetes.io/docs/concepts/storage/volumes/#nfs is:
With the feature tracked by this issue, Rook would be able to orchestrate/deploy NFS server instances (in addition to dynamically provisioning NFS volumes) so that they user doesn't have to do that themselves. |
Ah! Got it. Thanks |
What about adding support for the NFS Ganesha backend for Ceph (FS or RGW)? ceph-container already includes the packages so just a matter of exposing via Rook? |
Here is the design document for this feature request https://docs.google.com/document/d/1JTuSBudKD-DhEb6aWNCCVg7xP49f8FjPTSZlU-DOZRk/edit?usp=sharing |
Is this a bug report or feature request?
Feature Request
Are there any similar features already existing: Ceph is an existing storage backend for Rook and this would add NFS as another storage backend.
What should the feature do: From this feature, Rook would be able to orchestrate and deploy Network File System(s) in Kubernetes clusters.
What would be solved through this feature: Users would be able to setup and consume NFS storage.
Does this have an impact on existing features: #1375 is the overall design for adding new storage backends to Rook, the refactoring determined by that ticket will be needed to implement this one.
The text was updated successfully, but these errors were encountered: