Bug 1405307
| Summary: | PVC doesn't support mount option for NFS | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Kenjiro Nakayama <knakayam> |
| Component: | Storage | Assignee: | Hemant Kumar <hekumar> |
| Status: | CLOSED ERRATA | QA Contact: | Wenqi He <wehe> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3.0 | CC: | aos-bugs, bchilds, hchen, smunilla, wmeng |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
Feature:
Enable users to specify mount options with Persistent Volumes (including NFS and other volume types that support it). See openshift document for more information.
Reason:
Occasionally default mount options used by Openshift is not good enough for NFS and other volume types. This feature allows users to tweak mount options depending on their storage configuration.
Result:
Implemented support for mount options in NFS and other volume types that support it.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-10 05:17:28 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: | |||
|
Description
Kenjiro Nakayama
2016-12-16 07:26:07 UTC
to be addressed in Kubernetes 1.6 picked up in 1.6 rebase Added github pr link. Verified on below version:
openshift v3.6.86
kubernetes v1.6.1+5115d708d7
Now the pvc is supported mount option:
$ cat pvc.yaml
kind: PersistentVolume
apiVersion: v1
metadata:
name: pvmountopt
annotations:
volume.beta.kubernetes.io/mount-options: ro,nfsvers=3
spec:
capacity:
storage: 1Gi
accessModes:
- ReadWriteOnce
nfs:
path: /nfs
server: <nfserver>
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1716 |