Skip to content

Add documentation on storageClass.mountOptions and PV.mountOptions #5254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 1, 2017
Merged

Add documentation on storageClass.mountOptions and PV.mountOptions #5254

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3f0fbc3
Add documentation on storageClass.mountOptions and PV.mountOptions
Aug 30, 2017
d71e867
convert notes into callouts
chenopis Sep 1, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
convert notes into callouts
  • Loading branch information
@chenopis
chenopis authored Sep 1, 2017
commit d71e8670a64dde01d4487288c010ba5cda1c5023
12 changes: 8 additions & 4 deletions docs/concepts/storage/persistent-volumes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -232,8 +232,10 @@ Currently, only NFS and HostPath support recycling. AWS EBS, GCE PD, Azure Disk,

A Kubernetes administrator can specify additional mount options for when a Persistent Volume is mounted on a node.

Note that not all Persistent volume types support mount options. The following
volume types support mount options.
**Note:** Not all Persistent volume types support mount options.
{: .note}

The following volume types support mount options:

* GCEPersistentDisk
* AWSElasticBlockStore
Expand Down Expand Up @@ -339,8 +341,10 @@ to Kubernetes cluster by addon manager during installation.

When a PVC specifies a `selector` in addition to requesting a `StorageClass`,
the requirements are ANDed together: only a PV of the requested class and with
the requested labels may be bound to the PVC. Note that currently, a PVC with a
non-empty `selector` can't have a PV dynamically provisioned for it.
the requested labels may be bound to the PVC.

**Note:** Currently, a PVC with a non-empty `selector` can't have a PV dynamically provisioned for it.
{: .note}

In the past, the annotation `volume.beta.kubernetes.io/storage-class` was used instead
of `storageClassName` attribute. This annotation is still working, however
Expand Down