Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1417906 - Documentation on how to use nfs directly without PVC mechanism
Summary: Documentation on how to use nfs directly without PVC mechanism
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-31 12:00 UTC by Eduardo Minguez
Modified: 2019-08-10 06:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-10 06:40:24 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Eduardo Minguez 2017-01-31 12:00:52 UTC
Document URL: ?

Section Number and Name: none

Describe the issue: 
In k8s/ocp you can use nfs directly by specifying the volume as type nfs:

       volumes:
       - name: VOLUME1
         nfs:
           path: /path/to/export
           server: <fqdn>

By default, the scc restricted has this disabled, but you can create a new scc to support that.
In origin 1.1.5 ( https://github.com/openshift/origin/releases/tag/v1.1.5 ) there is a release note about this:
Administrators can now limit what volume types users can use directly from within a Pod - by default, regular users are now forbidden from directly mounting any of the remote volume type (they must use a PVC)

Suggestions for improvement: 
Add a section on how to create a nfs volume type, scc, etc.

Additional information:


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