Bug 1276084 - [DOCS] Information on securing PVs to namespaces with PVC.
[DOCS] Information on securing PVs to namespaces with PVC.
Status: CLOSED DUPLICATE of bug 1327308
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
3.0.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Ashley Hardin
Vikram Goyal
Vikram Goyal
:
Depends On: 1276082
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-28 12:20 EDT by Ryan Howe
Modified: 2016-06-02 10:50 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1276082
Environment:
Last Closed: 2016-06-02 10:50:13 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ryan Howe 2015-10-28 12:20:26 EDT
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. 

https://docs.openshift.com/enterprise/3.0/dev_guide/persistent_volumes.html#volume-and-claim-binding

https://docs.openshift.com/enterprise/3.0/rest_api/kubernetes_v1.html#v1-persistentvolumeclaim


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  


 apiVersion: v1
  kind: PersistentVolumeClaim
  metadata:
name: registry-claim
  spec:
accessModes:
- ReadWriteMany
resources:
  requests:
storage: 5Gi
volumeName: registry-volume
  status: {}



+++ 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.

https://docs.openshift.com/enterprise/3.0/rest_api/kubernetes_v1.html#v1-persistentvolume

Version-Release number of selected component (if applicable):
3.0.x
Comment 3 Ashley Hardin 2016-05-31 11:24:51 EDT
@Ryan
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:

https://docs.openshift.com/enterprise/3.2/install_config/persistent_storage/index.html

Thanks!
Comment 4 Ashley Hardin 2016-06-02 10:50:13 EDT
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 ***

Note You need to log in before you can comment on or make changes to this bug.