diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2017-11-13 20:01:51 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-11-13 20:01:51 -0800 |
| commit | 9d535acf15a366bf70bb5b21ed4698cae4c47189 (patch) | |
| tree | 9165f145a47cd7f53c951514ab93c2d6892c20fb | |
| parent | 62f13139cab5369fbbf6dc611ad72029e768ca84 (diff) | |
| parent | e81f02c0f0aa1b7240b980e900c1c051a7aca099 (diff) | |
Merge pull request #1393 from gin419/patch-7
Automatic merge from submit-queue.
Update propagation.md
| -rw-r--r-- | contributors/design-proposals/node/propagation.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/node/propagation.md b/contributors/design-proposals/node/propagation.md index 3c665552..959e69f9 100644 --- a/contributors/design-proposals/node/propagation.md +++ b/contributors/design-proposals/node/propagation.md @@ -294,7 +294,7 @@ may not propagate back to the host, depending of ordering of mount operations) 1. limitations this imposes on runtimes (RO-remounting may now affects the host, is it on purpose or a dangerous side-effect?) -1. A shared mount target imposes some costraints on its parent subtree (generally, +1. A shared mount target imposes some constraints on its parent subtree (generally, it has to be shared as well), which in turn prevents some mount operations when preparing a pod (eg. MS_MOVE). |