Storage Capacity Tracking

[pohly]

• One-line enhancement description (can be used as a release note): Supports exposing currently available storage capacity via CSIStorageCapacity objects and enhances scheduling of pods that use CSI volumes with late binding
• Kubernetes Enhancement Proposal PRs: Storage Capacity Constraints for Pod Scheduling #1353 and CSI inline volume size #1409
• KEP: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1472-storage-capacity-tracking
• Primary contact (assignee): @pohly
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.19
  • Beta release target (x.y): 1.21
  • Stable release target (x.y): 1.24
• Stable
  • KEP (k/enhancements) update PR(s): KEP-1472: storage capacity tracking: GA #3229
  • Code (k/k) update PR(s): storage capacity GA kubernetes#108445
  • Docs (k/website) update(s): Mark storage capacity as GA + related updates website#32008

[pohly]

/sig storage

[jeremyrickard]

Hey @pohly! 1.18 Enhancements lead here 👋 It looks like you've targeted 1.18 as the alpha release target for this.

he current release schedule is:
Monday, January 6th - Release Cycle Begins
Tuesday, January 28th EOD PST - Enhancements Freeze
Thursday, March 5th, EOD PST - Code Freeze
Monday, March 16th - Docs must be completed and reviewed
Tuesday, March 24th - Kubernetes 1.18.0 Released

To be included in the release, this enhancement must have a merged KEP in the implementable status. The KEP must also have graduation criteria and a Test Plan defined by Enhancement Freeze on January 28th..

If you could confirm that you're planning on releasing this as an alpha feature in 1.18, I'll add it to the milestone and update the release tracking sheet.

Thanks!

[pohly]

Jeremy Rickard <[email protected]> writes:

To be included in the release, this enhancement must have a merged KEP in the `implementable` status. The KEP must also have graduation criteria and a Test Plan defined by *Enhancement Freeze on January 28th*..

We are working on it.

If you could confirm that you're planning on releasing this as an alpha feature in 1.18, I'll add it to the milestone and update the release tracking sheet.

Yes, please do.

[jeremyrickard]

/milestone v1.18

[palnabarun]

@pohly Just a friendly reminder, we are less than 2 days away from the Enhancements Freeze (3PM Pacific Time, Tuesday, January 28th).

I see that the KEP PR is still open. Let us know if the release team can help in any way.

[jeremyrickard]

Hey @pohly, unfortunately we've hit enhancement freeze and the KEP PR hasn't merged. We're going to need to remove this from the 1.18 milestone and you'll need to file an Exception Request in order to get this back into 1.18.

[jeremyrickard]

/milestone clear

[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

[palnabarun]

/remove-lifecycle stale

[palnabarun]

Hi @pohly -- 1.19 Enhancements Lead here, I wanted to check in if you think this enhancement would graduate 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

[palnabarun]

Hi @pohly, pinging back as a reminder for the above. 🙂

[pohly]

@palnabarun: please track this for 1.19 as a new alpha feature.

The KEP still needs to be merged, but today we reached an agreement how we'll get there.

[palnabarun]

@pohly -- Sure. I am going ahead and marking this enhancement At Risk since the KEP PR in flight.

Please keep a note of the requirements for Enhancements Freeze:

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.

In addition to the above, #1620 merged recently, adding production readiness review questions to the KEP template. We are not making it mandatory for the 1.19 release cycle, but it would be great if the PRR questionnaire is filled since the KEP PR is in flight.

[palnabarun]

/stage alpha
/milestone v1.19

[pohly]

@kubernetes/enhancements : please add this back as "tracked/yes" with the goal of reaching GA in 1.24.

An exception request for that was submitted and granted: https://groups.google.com/g/kubernetes-sig-release/c/sUpd2H1wxnk/m/lL_I6GT-BwAJ

[gracenng]

Hi @pohly , the enhancement will be marked at tracked/yes once it has met all the requirements for Enhancement Freeze. We're awaiting #3229 to merge :)

[gracenng]

Hi @pohly, does this enhancement need docs?

[pohly]

Yes. The docs PR was already created and is listed in the description.

[gracenng]

Hi @pohly 1.24 Enhancements Team here,
With Code Freeze approaching on 18:00 PDT Tuesday March 29th 2022, we are currently tracking the following k/k PR:

• storage capacity GA kubernetes#108445

The status of this enhancement is at risk until the PR is merged. Please let me know if I'm missing any. Thanks!

[gracenng]

Marking this as tracked for Code Freeze. Let me know if there's any other k/k PR!

[Priyankasaggu11929]

Hello @pohly 👋, 1.25 Enhancements team here.

This feature has been fully implemented and is now GA in K8s version 1.24. 🎉

Please update the kep.yaml file's status to implemented and close this issue.

This would help accurate tracking in the v1.25 cycle. Thank you so much! 🙂

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[pohly]

/close

Feature is complete and marked as "implemented" in the kep.yaml.

[k8s-ci-robot]

@pohly: Closing this issue.

In response to this:

/close

Feature is complete and marked as "implemented" in the kep.yaml.

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.