diff options
| author | Hemant Kumar <hekumar@redhat.com> | 2017-03-28 16:28:37 -0400 |
|---|---|---|
| committer | Hemant Kumar <hekumar@redhat.com> | 2017-03-28 16:29:40 -0400 |
| commit | 689dd62237d54cd3ff638263f15010daebe904d1 (patch) | |
| tree | 4f22f7a6109af9ed459da28f97d13840ec6beb7c | |
| parent | 4605abfa0755e7741907db0bc7f131edd0406242 (diff) | |
Fix mount options proposal to be accurate
| -rw-r--r-- | contributors/design-proposals/mount-options.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/contributors/design-proposals/mount-options.md b/contributors/design-proposals/mount-options.md index 0fb88db0..4d4de87f 100644 --- a/contributors/design-proposals/mount-options.md +++ b/contributors/design-proposals/mount-options.md @@ -15,7 +15,7 @@ Mount time options that are operationally important and have no security implica We are going to add support for mount options in PVs as a beta feature to begin with. -Mount options can be specified as `mountOptions` annotations in PV. For example: +Mount options can be specified as `mount-options` annotations in PV. For example: ``` yaml apiVersion: v1 @@ -23,7 +23,7 @@ Mount options can be specified as `mountOptions` annotations in PV. For example: metadata: name: pv0003 annotations: - volume.beta.kubernetes.io/mountOptions: "hard,nolock,nfsvers=3" + volume.beta.kubernetes.io/mount-options: "hard,nolock,nfsvers=3" spec: capacity: storage: 5Gi @@ -42,7 +42,7 @@ While mount options enable more flexibility in how volumes are mounted, it can r in user specifying options that are not supported or are known to be problematic when using inline volume specs. -After much deliberation it was decided that - `mountOptions` as an API parameter will not be supported +After much deliberation it was decided that - `mount-options` as an API parameter will not be supported for inline volume specs. ### Error handling and plugins that don't support mount option |