Skip to content
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.

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

Documentation for MountPropagation beta #7655

Merged
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
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
12 changes: 4 additions & 8 deletions docs/concepts/storage/volumes.md
Original file line number Diff line number Diff line change
Expand Up @@ -1002,9 +1002,7 @@ More details can be found [here](https://github.com/kubernetes/community/blob/ma

## Mount propagation

**Note:** Mount propagation is an alpha feature in Kubernetes 1.8 and may be
redesigned or even removed in future releases.
{: .note}
{% assign for_k8s_version="v1.10" %}{% include feature-state-beta.md %}

Mount propagation allows for sharing volumes mounted by a Container to
other Containers in the same Pod, or even to other Pods on the same node.
Expand All @@ -1013,14 +1011,12 @@ If the "`MountPropagation`" feature is disabled, volume mounts in pods are not p
That is, Containers run with `private` mount propagation as described in the
[Linux kernel documentation](https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt).

To enable this feature, specify `MountPropagation=true` in the
`--feature-gates` command line option for the API server and kubelets.
When enabled, the `volumeMounts` field of a Container has a new
`mountPropagation` subfield. Its values are:
Mount propagation of a volume is controlled by `mountPropagation` field in Container.volumeMounts.
Its values are:

* `HostToContainer` - This volume mount will receive all subsequent mounts
that are mounted to this volume or any of its subdirectories. This is
the default mode when the MountPropagation feature is enabled.
the default mode.

In other words, if the host mounts anything inside the volume mount, the
Container will see it mounted there.
Expand Down
1 change: 1 addition & 0 deletions docs/reference/feature-gates.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,7 @@ different Kubernetes components.
| `LocalStorageCapacityIsolation` | `true` | Beta| 1.10 | |
| `MountContainers` | `false` | Alpha | 1.9 | |
| `MountPropagation` | `false` | Alpha | 1.8 | |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We keep tracking the status of each feature gates so you may want to revise this line AND add the following line:

| `MountPropagation` | `false` | Alpha | 1.8 | 1.9  |

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit ... line 63 should read

 | `MountPropagation` | `false` | Alpha | 1.8 | 1.9 |

This clearly indicates that the Alpha stage ends at 1.9 version.

| `MountPropagation` | `true` | Beta | 1.10 | |
| `PersistentLocalVolumes` | `false` | Alpha | 1.7 | |
| `PodPriority` | `false` | Alpha | 1.8 | |
| `PVCProtection` | `false` | Alpha | 1.9 | |
Expand Down