We need to expand information on how an systems admin would secure a PV so that a system admin can control what PV a claim uses.
We can create a PVC with the volumeName but looking for use case in the docs for this and also information on how a sysadmin would limit project admin from creating a PVC that just binds to an available PV
+++ This bug was initially created as a clone of Bug #1276082 +++
Description of problem:
PV needs to be able to be secured down so that claims can auto bind to the available PVs for the namespace.
Admin are looking for a way to provision Persistent Volumes that are only available to a defined namespace. While at the same time allowing the user to provision their own PVCs.
Version-Release number of selected component (if applicable):
OSE 3.2 docs included new information on configuring persistent storage. Please review these new topics and let me know if there is still an issue or anything else that should be added:
After discussion with Ryan Howe, it was determined that this a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1284994 and https://bugzilla.redhat.com/show_bug.cgi?id=1327308
*** This bug has been marked as a duplicate of bug 1327308 ***