Supports Storage as Allocatable Resource

[jingxu97]

Feature Description

• One-line feature description (can be used as a release note): Supports storage as part of the node allocatable resources in a similar way as CPU and memory.
• Primary contact (assignee): @vishh @jingxu97
• Responsible SIGs: @kubernetes/sig-storage-feature-requests
• Design proposal link (community repo): [Proposal] Improve Local Storage Management community#306
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @derekwaynecarr, @vishh, @dashpole
• Approver (likely from SIG/area to which feature belongs): @thockin, @vishh, @derekwaynecarr
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y): 1.7
  • Beta release target (x.y): 1.10
  • Stable release target (x.y): 1.11

[idvoretskyi]

@jingxu97 @vishh @kubernetes/sig-storage-feature-requests any updates for 1.8? Is this feature still on track for the release?

[jingxu97]

This feature is on track for the release. #43607 tracks all the changes. But this is still Alpha feature.

[idvoretskyi]

@jingxu97 please, update the features tracking board with the relevant data.

[jdumars]

@jingxu97 any update on missing docs? PR is due today.

[jingxu97]

Sorry for the delay. I filed PR to update the doc kubernetes/website#5490

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

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

[jingxu97]

In Kuberentes, ephemeral storage is added as one resource type for allocatable resource. Since allocatable resource is already GA, so the work for this feature is finished for open source part.
cc @dashpole @vishh Could you approve this feature?

[jingxu97]

/remove-lifecycle stale

[justaugustus]

@vishh / @jingxu97 --
What's the current status of this feature? From the comments, it looks like it's complete, but I'd like to make sure before we look at closing this out.

cc @idvoretskyi

[jingxu97]

@justaugustus Yes, the work for this feature is basically done. We are moving to beta in 1.10. Thanks!

[justaugustus]

@jingxu97 just to clarify, would you mind updating the feature description, especially the feature targets?

[jingxu97]

@justaugustus updated. Thanks!

[justaugustus]

This feature current has no 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

Once this feature is appropriately updated, please explicitly ping @justaugustus, @kacole2, @robertsandoval, @rajendar38 to note that it is ready to be included in the Features Tracking Spreadsheet for Kubernetes 1.12.

---

Please note that Features Freeze is tomorrow, 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!

P.S. This was sent via automation

[kacole2]

Hi
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!

[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

[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

[msedzins]

Hey there @jingxu97, @vishh -- 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?

In order to have this part of the release:

1. The KEP PR must be merged in an implementable state
2. The KEP must have test plans
3. The KEP must have graduation criteria.

The current release schedule is:

• Monday, April 13: Week 1 - Release cycle begins
• Tuesday, May 19: Week 6 - Enhancements Freeze
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released
• Thursday, August 20: Week 19 - Release Retrospective

If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[msedzins]

Hi there @jingxu97 , @vishh

Kind reminder about my question above.

Regards,
Mirek

[msedzins]

Hi there @jingxu97 , @vishh

Kind reminder about my question above.

Regards,
Mirek

[msedzins]

Hi there @jingxu97 , @vishh

Kind reminder about my question above.

Regards,
Mirek

[msau42]

There are no plans to graduate this feature in 1.19

[msedzins]

Thank you @msau42 for letting me know.

[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

[warmchang]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @msau42 @pohly

Enhancements Lead here. Any plans for this to graduate in 1.20?

Thanks,
Kirsten

[kikisdeliveryservice]

Hi @msau42 @pohly

Following up: 1.20 Enhancements Freeze is October 6th. Could you let us know if you are planning to GA in 1.20? To be included in the milestone:
The KEP must be merged in an implementable state
The KEP must have test plans
The KEP must have graduation criteria

Also, the linked design proposal is quite old and not in the current format, see for ref https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template

Thanks,
Kirsten

[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

[immanuelfodor]

/remove-lifecycle stale

[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-contributor-experience at kubernetes/community.
/lifecycle stale

[frittentheke]

/remove-lifecycle stale

[immanuelfodor]

/lifecycle frozen

[immanuelfodor]

I don't know if it's against the rules to make it frozen but it started to be annoying :D If you think it's better to bump it up constantly, then please set accordingly.

[fejta-bot]

Enhancement issues opened in kubernetes/enhancements should never be marked as frozen.
Enhancement Owners can ensure that enhancements stay fresh by consistently updating their states across release cycles.

/remove-lifecycle frozen

[BenTheElder]

/lifecycle frozen
kubernetes/test-infra#22488