Mount namespace propagation

[saad-ali]

Feature Description

• One-line feature description (can be used as a release note): Enable a container to mount a volume rshared so that any mounts from inside the container are reflected in the host's mount namespace (this will enable, for example, containerization of volume plugins).
• Primary contact (assignee): @jsafrane
• Responsible SIGs: /sig-storage
• Design proposal link (community repo): Redesign mount propagation community#659
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
  • @saad-ali
  • @childsb
• Approver (likely from SIG/area to which feature belongs):
  • @thockin
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y): 1.8
  • Beta release target (x.y): 1.10
  • Stable release target (x.y): 1.12?

[saad-ali]

Split this out from #278

[saad-ali]

Design doc: kubernetes/community#659 by @jsafrane

Implemented in PR kubernetes/kubernetes#46444 for 1.8 by @jsafrane

[saad-ali]

Need user docs @jsafrane

[jsafrane]

Docs: kubernetes/website#5544

[jbw976]

What are the plans for getting this mount propagation feature to beta status in 1.9? Will it be available without a feature gate in 1.9? The Rook team would love to start using this feature by default as soon as possible.

I don't see it tracked in the SIG Storage 1.9 planning sheet, should it be tracked there? https://docs.google.com/spreadsheets/d/1t4z5DYKjX2ZDlkTpCnp18icRAQqOE85C1T1r2gqJVck/edit?usp=sharing

[jsafrane]

It's planned for 1.10, volunteers needed. We need more tests:

• Together with CSI.
• Check various recent and "long-term support" distros.
• Add Kubernetes e2e tests for existing in-tree volume plugins (Gluster, Ceph, ...) using containerized mount utilities - this will stress test it quite a lot.

[idvoretskyi]

/assign @jsafrane

[Bradamant3]

@jsafrane Docs update, please! Also please update the feature tracking spreadsheet. We need the docs asap. PR merges are due this Friday (March 9). Thanks!

[jsafrane]

Docs: kubernetes/website#7655

[justaugustus]

@jsafrane
Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

• Description
• Milestone
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

cc @idvoretskyi

[jsafrane]

@saad-ali, shall we bake it as Beta for one more release and have it stable in 1.12?

[justaugustus]

@jsafrane I'll tentatively set this to next-milestone, but if you feel differently, just let us know.

[zparnold]

Hey there! @saad-ali I'm the wrangler for the Docs this release. Is there any chance I could have you open up a docs PR against the release-1.12 branch as a placeholder? That gives us more confidence in the feature shipping in this release and gives me something to work with when we start doing reviews/edits. Thanks! If this feature does not require docs, could you please update the features tracking spreadsheet to reflect it?

[jsafrane]

Filled kubernetes/website#10090.

[zparnold]

Thank you!

…

On Mon, Aug 27, 2018 at 1:09 AM Jan Šafránek ***@***.***> wrote: Filled kubernetes/website#10090 <kubernetes/website#10090>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#432 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE81SIz7Kl8e0omBOriOlnUruyZwqnSvks5uU6kkgaJpZM4PbQ1A> .

[kacole2]

@saad-ali @jsafrane It looks like this feature made it to GA and has docs in place. Are we good to close?

[jsafrane]

Yes, this is GA now and could be closed (not sure what's the policy here).

[kacole2]

/close

[k8s-ci-robot]

@kacole2: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.