You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What should the feature do:
Currently, the ceph filesystem supports in Rook requires the user to create a external storage cephfs provisioner to provision cephfs volume that will be consumed by a pod. The user has to look up the IP address of the Mon IP address, run a external storagre provisioner pod , etc., which is a cumbersome experience. This could be improved by intergrating a dynamic provisioner in rook operator that would automiatically do those actions for the user and generate a PV without user intervention. All the user who wants to request a PVC needs to do is deploying ceph filesystem firstly and declare a PVC with a storageclass.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Is this a bug report or feature request?
What should the feature do:
Currently, the ceph filesystem supports in Rook requires the user to create a external storage cephfs provisioner to provision cephfs volume that will be consumed by a pod. The user has to look up the IP address of the Mon IP address, run a external storagre provisioner pod , etc., which is a cumbersome experience. This could be improved by intergrating a dynamic provisioner in rook operator that would automiatically do those actions for the user and generate a PV without user intervention. All the user who wants to request a PVC needs to do is deploying ceph filesystem firstly and declare a PVC with a storageclass.
The text was updated successfully, but these errors were encountered: