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

Local storage dynamic provisioning #562

Closed
lichuqiang opened this Issue Apr 17, 2018 · 18 comments

Comments

Projects
None yet
9 participants
@lichuqiang
Copy link
Member

lichuqiang commented Apr 17, 2018

Feature Description

  • One-line feature description (can be used as a release note): Local storage dynamic provisioning
  • Primary contact (assignee): @lichuqiang @msau42
  • Responsible SIGs: sig-storage
  • Design proposal link (community repo): kubernetes/community#1914
  • Link to e2e and/or unit tests:
  • Reviewer(s): @msau42 @jsafrane
  • Approver (likely from SIG/area to which feature belongs): @msau42
  • Feature target (which target equals to which milestone):
    • Alpha release target (x.y) 1.12
    • Beta release target (x.y) 1.13
    • Stable release target (x.y) 1.14
@lichuqiang

This comment has been minimized.

Copy link
Member Author

lichuqiang commented Apr 17, 2018

/assign

@justaugustus

This comment has been minimized.

Copy link
Member

justaugustus commented Jun 4, 2018

@lichuqiang @msau42 -- We're doing one more sweep of the 1.11 Features tracking spreadsheet.
Would you mind filling in any incomplete / blank fields for this feature's line item?

@lichuqiang

This comment has been minimized.

Copy link
Member Author

lichuqiang commented Jun 4, 2018

Sorry, I think the feature will have to be delayed to v1.12 due to some dependency issue.

@justaugustus justaugustus removed this from the v1.11 milestone Jun 4, 2018

@justaugustus

This comment has been minimized.

Copy link
Member

justaugustus commented Jun 4, 2018

Thanks for the update, @lichuqiang!

@saad-ali saad-ali added this to the v1.12 milestone Jun 4, 2018

@justaugustus

This comment has been minimized.

Copy link
Member

justaugustus commented Jul 18, 2018

@lichuqiang @msau42 @kubernetes/sig-storage-feature-requests --

This feature was removed from the previous milestone, so we'd like to check in and see if there are any plans for this in Kubernetes 1.12.

If so, please ensure that this issue is up-to-date with ALL of the following information:

  • One-line feature description (can be used as a release note):
  • Primary contact (assignee):
  • Responsible SIGs:
  • Design proposal link (community repo):
  • Link to e2e and/or unit tests:
  • Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
  • Approver (likely from SIG/area to which feature belongs):
  • Feature target (which target equals to which milestone):
    • Alpha release target (x.y)
    • Beta release target (x.y)
    • Stable release target (x.y)

Set the following:

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

Please note that the Features Freeze is July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

  • Docs deadline (open placeholder PRs): 8/21
  • Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

/cc @justaugustus @kacole2 @robertsandoval @rajendar38

@lichuqiang

This comment has been minimized.

Copy link
Member Author

lichuqiang commented Jul 18, 2018

@justaugustus, Thank you for your reminding!
I think most of the information is up-to-date.
We'll probably have an update on detail of the proposal later, but it will always happen in the same PR :)

@justaugustus

This comment has been minimized.

Copy link
Member

justaugustus commented Jul 18, 2018

Thanks @lichuqiang!

@zparnold

This comment has been minimized.

Copy link
Member

zparnold commented Aug 20, 2018

Hey there! @lichuqiang 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?

@justaugustus

This comment has been minimized.

Copy link
Member

justaugustus commented Sep 5, 2018

@lichuqiang @msau42 -- Any update on docs status for this feature? Are we still planning to land it for 1.12?
At this point, code freeze is upon us, and docs are overdue.
If we don't here anything back regarding this feature ASAP, we'll need to remove it from the milestone.

cc: @zparnold @jimangel @tfogo

@msau42

This comment has been minimized.

Copy link
Member

msau42 commented Sep 5, 2018

No, this feature is not going to make 1.12

@justaugustus

This comment has been minimized.

Copy link
Member

justaugustus commented Sep 5, 2018

Got it. Thanks for the update!
/milestone clear

@justaugustus justaugustus added tracked/no and removed tracked/yes labels Sep 5, 2018

@justaugustus justaugustus removed this from the v1.12 milestone Sep 5, 2018

@kacole2

This comment has been minimized.

Copy link
Member

kacole2 commented Oct 8, 2018

Hi @msau42 @lichuqiang
This enhancement has been tracked before, so we'd like to check in and see if there are any plans for this to graduate stages in Kubernetes 1.13. This release is targeted to be more ‘stable’ and will have an aggressive timeline. Please only include this enhancement if there is a high level of confidence it will meet the following deadlines:
Docs (open placeholder PRs): 11/8
Code Slush: 11/9
Code Freeze Begins: 11/15
Docs Complete and Reviewed: 11/27

Please take a moment to update the milestones on your original post for future tracking and ping @kacole2 if it needs to be included in the 1.13 Enhancements Tracking Sheet

Thanks!

@msau42

This comment has been minimized.

Copy link
Member

msau42 commented Oct 8, 2018

This quarter will be focusing on design and prototyping, so no feature deliverables for 1.13

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Jan 6, 2019

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

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Feb 5, 2019

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

@pohly

This comment has been minimized.

Copy link

pohly commented Feb 6, 2019

/remove-lifecycle stale

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Mar 8, 2019

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

This comment has been minimized.

Copy link
Contributor

k8s-ci-robot commented Mar 8, 2019

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.