3. What is the nature and description of the request?
	If OSE end user create PVC in project/namespace it should be able to utilize it from application (pod/container) also created in the same project/namespace out of box. Currently is it not the case with dynamically provisioned persistent volumes, in pod log we see "Permission denied" exceptions.

4. Why does the customer need this? (List the business requirements here) 
	This is something what we consider as standard use case for OSE customers.

5. How would the customer like to achieve this? (List the functional requirements here)
	This should be automated within OSE itself.

6. For each functional requirement listed in question 5, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
	a. OSE end user create PVC (with annotations volume.alpha.kubernetes.io/storage-class)
	b. OSE end user create new application that utilize newly created PVC
	c. Application works without exceptions
		c.1. oc logs pod-id
		c.2 oc rsc pod-id  # and we can check that at mount point app created files

7. Is there already an existing RFE upstream or in Red Hat bugzilla?
	> N/A

8. Does the customer have any specific timeline dependencies?
	We would need this until July 2016.

9. Is the sales team involved in this request and do they have any additional input?
	No

10. List any affected packages or components. 
	OSE part responsible for persistent volumes

11. Would the customer be able to assist in testing this functionality if implemented?
	Yes