Bug 1417906
| Summary: | Documentation on how to use nfs directly without PVC mechanism | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Eduardo Minguez <eminguez> |
| Component: | Documentation | Assignee: | Vikram Goyal <vigoyal> |
| Status: | CLOSED EOL | QA Contact: | Vikram Goyal <vigoyal> |
| Severity: | unspecified | Docs Contact: | Vikram Goyal <vigoyal> |
| Priority: | unspecified | ||
| Version: | 3.4.0 | CC: | aos-bugs, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-10 06:40:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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: