Enhancements: Implements Raw Block Volume Support for in-tree vSphere plugin

[fanzhangio]

Feature Description

• One-line feature description (can be used as a release note):
  
  
  
  • vSphereVolume implements Raw Block Volume Support
  
  
• Primary contact (assignee): @fanzhangio
• Responsible SIGs: sig-storage
• Reviewer(s): @vladimirvivien @divyenpatel
• Approver (likely from SIG/area to which feature belongs): @saad-ali @divyenpatel
• Feature target (which target equals to which milestone):
  
  
  
  • Alpha release target (x.y) 1.13
  
  
  • Beta release target (x.y) 1.13
  
  
  • Stable release target (x.y) 1.13
  
  

[fanzhangio]

/assign

[fanzhangio]

/milestone 1.13

[k8s-ci-robot]

@fanzhangio: You must be a member of the kubernetes/kubernetes-milestone-maintainers github team to set the milestone.

In response to this:

/milestone 1.13

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.

[fanzhangio]

/sig storage

[fanzhangio]

/kind feature

[fanzhangio]

/stage alpha

[kacole2]

/milestone v1.13

[spiffxp]

@fanzhangio @saad-ali @jsafrane are there issues or PR's in k/k we can link to track this work?

[fanzhangio]

PR https://github.com/kubernetes/kubernetes/pull/68761

@spiffxp Thank you.

[tfogo]

Hi @fanzhangio , I'm the docs wrangler for the 1.13 release. Could you please open a placeholder PR for the docs for this enhancement against the dev-1.13 branch of k/website and send me a link? If this doesn't require docs in k/website, please let me know.

The deadline for placeholder PRs for the 1.13 release is November 8. So it's important to make a docs PR as soon as possible.

If you have any questions about any of this, I'm happy to help. You can also message me on slack (I'm tfogo there too). 😀

Thanks! ✨

[vladimirvivien]

@tfogo thanks. We'll make sure there is documentation ready.

[vladimirvivien]

Documentation PR - https://github.com/kubernetes/website/pull/10932

[kacole2]

@fanzhangio is this feature only related to vSphere In-tree driver? That was missing before but it's good to know.

[fanzhangio]

@kacole2 Yes, this feature is changed to relating to in-tree vSphereVolume. The implementation PR https://github.com/kubernetes/kubernetes/pull/68761 has been merged recently. Sorry for any confusion.

[AishSundar]

@vladimirvivien @fanzhangio can you plz confirm if we are waiting on any more PRs for this enhancement (other than the docs one)?

[nikopen]

This PR hasn't had much progress in the last weeks: https://github.com/kubernetes/kubernetes/pull/67465

@fanzhangio I suppose it's required, are you sure it's gonna make it in the following 5-10 days?

[vladimirvivien]

There has been a change (a mixed up really). PR kubernetes/kubernetes#67465 is not being tracked and will not make it for this release. Instead, this feature has been updated to track - https://github.com/kubernetes/kubernetes/pull/68761

Summary

• Related PR merged - https://github.com/kubernetes/kubernetes/pull/68761
• Documentation PR - kubernetes/website#10932

This is good to go.

cc @nikopen

[kacole2]

@vladimirvivien do you know which enhancement issue kubernetes/kubernetes#67465 should be attached to? Thanks for letting me know about the mix up. I'll make adjustments in the sheet. This one is all GTG!

[vladimirvivien]

@kacole2 #67465 will not be attached to any enhancement for 1.13. We will revisit in 1.14.

[claurence]

@fanzhangio Hello - I’m the enhancement’s lead for 1.14 and I’m checking in on this issue to see what work (if any) is being planned for the 1.14 release. Enhancements freeze is Jan 29th and I want to remind that all enhancements must have a KEP - I can't find a KEP for this issue can you please drop a link to the KEP? Thanks

[lachie83]

@fanzhangio 👋1.14 release enhancements shadow here. We are less than a week out from 1.14 enhancements freeze. Friendly ping on @claurence comment above.

[claurence]

@fanzhangio @vladimirvivien checking in on plans for this issue for 1.14? Is there a KEP associated with it? We'd like all issues to have a KEP before enhancement freeze

[claurence]

@fanzhangio @vladimirvivien since there is no KEP for this issue yet we will be removing it from the 1.14 milestone. To have it added back in please file an exception - information on the exception process can be found here: https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

[kacole2]

Hello, I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet.

Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[evillgenius75]

Hi @fanzhangio , I'm the 1.16 Enhancement Shadow. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheet.

Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.

As a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements. If you have a KEP please link here

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.

[kacole2]

From @fanzhangio:
Hi Kendrick, this feature has been updated to track - kubernetes/kubernetes#68761
Related PR merged - kubernetes/kubernetes#68761
Documentation PR - kubernetes/website#10932
All of them are merged in release 1.13