Flex volume API and Improved lifecycle (flexvolume)

[chakri-nelluri]

Description

Existing flex volume plugin enables administrators/vendors to create out-of-tree volume plugins, i.e., plugins which do not reside in Kubernetes project. But, it has the following gaps.

It lacks support for the latest enhancements to in-tree plugins like dynamic provisioning and centralized attach-detach controller
It does not define a stable driver api for administrators/vendors to work.
The current flex volume plugin deployment model is not suitable for environments like GCE & CoreOS, where access to the root file system is restricted. And in other environments the overall user experience is poor, as it requires manual installation of the plugin on every node and restart of kubelets & controller manager.

Progress Tracker

• Before Alpha
  • Write and maintain draft quality doc
    • During development keep a doc up-to-date about the desired experience of the feature and how someone can try the feature in its current state. Think of it as the README of your new feature and a skeleton for the docs to be written before the Kubernetes release. Paste link to Google Doc: DOC-LINK
  • Design Approval
    • Design Proposal. This goes under docs/proposals. Doing a proposal as a PR allows line-by-line commenting from community, and creates the basis for later design documentation. Paste link to merged design proposal here: PROPOSAL-NUMBER
    • Decide which repo this feature's code will be checked into. Not everything needs to land in the core kubernetes repo. REPO-NAME
    • Initial API review (if API). Maybe same PR as design doc. PR-NUMBER
      • Any code that changes an API (/pkg/apis/...)
      • cc @kubernetes/api
    • Identify shepherd (your SIG lead and/or kubernetes-pm@googlegroups.com will be able to help you). My Shepherd is: replace.me@replaceme.com (and/or GH Handle)
      • A shepherd is an individual who will help acquaint you with the process of getting your feature into the repo, identify reviewers and provide feedback on the feature. They are not (necessarily) the code reviewer of the feature, or tech lead for the area.
      • The shepherd is not responsible for showing up to Kubernetes-PM meetings and/or communicating if the feature is on-track to make the release goals. That is still your responsibility.
    • Identify secondary/backup contact point. My Secondary Contact Point is: replace.me@replaceme.com (and/or GH Handle)
  • Write (code + tests + docs) then get them merged. ALL-PR-NUMBERS
    • Code needs to be disabled by default. Verified by code OWNERS
    • Minimal testing
    • Minimal docs
      • cc @kubernetes/docs on docs PR
      • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
      • New apis: Glossary Section Item in the docs repo: kubernetes/kubernetes.github.io
    • Update release notes
• Before Beta
  • Testing is sufficient for beta
  • User docs with tutorials
    • Updated walkthrough / tutorial in the docs repo: kubernetes/kubernetes.github.io
    • cc @kubernetes/docs on docs PR
    • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
  • Thorough API review
    • cc @kubernetes/api
• Before Stable
  • docs/proposals/foo.md moved to docs/design/foo.md
    • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
  • Soak, load testing
  • detailed user docs and examples
    • cc @kubernetes/docs
    • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

FEATURE_STATUS is used for feature tracking and to be updated by @kubernetes/feature-reviewers.
FEATURE_STATUS: IN_DEVELOPMENT

More advice:

Design

• Once you get LGTM from a @kubernetes/feature-reviewers member, you can check this checkbox, and the reviewer will apply the "design-complete" label.

Coding

• Use as many PRs as you need. Write tests in the same or different PRs, as is convenient for you.
• As each PR is merged, add a comment to this issue referencing the PRs. Code goes in the http://github.com/kubernetes/kubernetes repository,
  and sometimes http://github.com/kubernetes/contrib, or other repos.
• When you are done with the code, apply the "code-complete" label.
• When the feature has user docs, please add a comment mentioning @kubernetes/feature-reviewers and they will
  check that the code matches the proposed feature and design, and that everything is done, and that there is adequate
  testing. They won't do detailed code review: that already happened when your PRs were reviewed.
  When that is done, you can check this box and the reviewer will apply the "code-complete" label.

Docs

• Write user docs and get them merged in.
• User docs go into http://github.com/kubernetes/kubernetes.github.io.
• When the feature has user docs, please add a comment mentioning @kubernetes/docs.
• When you get LGTM, you can check this checkbox, and the reviewer will apply the "docs-complete" label.

[chakri-nelluri]

@gr4701 @thockin @philips Create new Feature request for Flex volume proposals:
kubernetes/kubernetes#32543
kubernetes/kubernetes#32550

[idvoretskyi]

@chakri-nelluri can you provide the actual status of the feature? Which SIG is responsible for it?

[saad-ali]

@kubernetes/sig-storage is responsible for this feature.

It is not part of 1.5

[idvoretskyi]

@saad-ali thank you!

[idvoretskyi]

@saad-ali which release does this feature target and which stage (alpha/beta/stable)?

[mdelio]

@idvoretskyi alpha in 1.6

[idvoretskyi]

@chakri-nelluri @mdelio please, provide us with the release notes and documentation PR (or links) at https://docs.google.com/spreadsheets/d/1nspIeRVNjAQHRslHQD1-6gPv99OcYZLMezrBe3Pfhhg/edit#gid=0

[jaredbhatti]

Pingity ping. Is there a Docs PR for this? Is one needed?

[childsb]

@jaredbhatti is this enough for docs: kubernetes/kubernetes#43326 or do we need a PR against kubernetes/kubernetes.github.io also?

[jaredbhatti]

This looks like a pretty sizable feature that folks around going to want to know about. The current documentation is pretty slim, but if the readme is enough for current users, I'm fine with it. This is what exists now: https://kubernetes.io/docs/user-guide/volumes/#flexvolume

…

On Fri, Mar 17, 2017 at 3:04 PM, bradley childs ***@***.***> wrote: @jaredbhatti <https://github.com/jaredbhatti> is this enough for docs: kubernetes/kubernetes#43326 <kubernetes/kubernetes#43326> or do we need a PR against kubernetes/kubernetes.github.io also? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#93 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AF3Lgt4nUsb7TXu-oXINjaaiMIfvhLBfks5rmwN4gaJpZM4J8Hyy> .

[chakri-nelluri]

@jaredbhatti more documentation is at: https://github.com/kubernetes/kubernetes/tree/master/examples/volumes/flexvolume The open PR kubernetes/kubernetes#43326 updates this documentation to reflect 1.6 changes. Let me know if there is any other place holder to include this documentation. I will update it. Thanks ~Chakri

…

On Fri, Mar 17, 2017 at 3:32 PM, Jared ***@***.***> wrote: This looks like a pretty sizable feature that folks around going to want to know about. The current documentation is pretty slim, but if the readme is enough for current users, I'm fine with it. This is what exists now: https://kubernetes.io/docs/user-guide/volumes/#flexvolume On Fri, Mar 17, 2017 at 3:04 PM, bradley childs ***@***.***> wrote: > @jaredbhatti <https://github.com/jaredbhatti> is this enough for docs: > kubernetes/kubernetes#43326 > <kubernetes/kubernetes#43326> or do we need a PR > against kubernetes/kubernetes.github.io also? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#93 (comment) >, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AF3Lgt4nUsb7TXu- oXINjaaiMIfvhLBfks5rmwN4gaJpZM4J8Hyy> > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#93 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJdfb7H6oqRES-yRSoLpvccAffToIcccks5rmwoYgaJpZM4J8Hyy> .

[calebamiles]

@chakri-nelluri, please confirm with @saad-ali and @devin-donnelly that no updates are needed to the user facing documentation at k8s.io.

cc: @ethernetdan, @kubernetes/release-team

[chakri-nelluri]

/close

[luxas]

@chakri-nelluri Where is this feature or its successor now tracked?

[zhangxiaoyu-zidif]

@luxas
After I check these features. It seems that these two features are both abandoned.
Sad :(

[chakri-nelluri]

Hi @luxas this will be superseded by CSI. https://github.com/container-storage-interface/spec

[luxas]

@chakri-nelluri So #178 is the successor, right?

[chakri-nelluri]

@luxas. Yes #178 is the successor. Thanks