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

Storage Capacity Tracking #1472

Closed
2 of 4 tasks
pohly opened this issue Jan 20, 2020 · 58 comments
Closed
2 of 4 tasks

Storage Capacity Tracking #1472

pohly opened this issue Jan 20, 2020 · 58 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Milestone

Comments

@pohly
Copy link
Contributor

pohly commented Jan 20, 2020

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 20, 2020
@pohly
Copy link
Contributor Author

pohly commented Jan 20, 2020

/sig storage

@k8s-ci-robot k8s-ci-robot added sig/storage Categorizes an issue or PR as relevant to SIG Storage. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jan 20, 2020
@jeremyrickard
Copy link
Contributor

jeremyrickard commented Jan 20, 2020

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
Copy link
Contributor Author

pohly commented Jan 20, 2020

@jeremyrickard jeremyrickard added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jan 23, 2020
@jeremyrickard
Copy link
Contributor

jeremyrickard commented Jan 23, 2020

/milestone v1.18

@palnabarun
Copy link
Member

palnabarun commented Jan 27, 2020

@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
Copy link
Contributor

jeremyrickard commented Jan 29, 2020

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
Copy link
Contributor

jeremyrickard commented Jan 29, 2020

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.18 milestone Jan 29, 2020
@jeremyrickard jeremyrickard added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Jan 29, 2020
@fejta-bot
Copy link

fejta-bot commented Apr 28, 2020

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 28, 2020
@palnabarun
Copy link
Member

palnabarun commented Apr 28, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 28, 2020
@palnabarun
Copy link
Member

palnabarun commented Apr 28, 2020

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
Copy link
Member

palnabarun commented May 11, 2020

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

@pohly
Copy link
Contributor Author

pohly commented May 13, 2020

@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
Copy link
Member

palnabarun commented May 13, 2020

@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
Copy link
Member

palnabarun commented May 13, 2020

/stage alpha
/milestone v1.19

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label May 13, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.19 milestone May 13, 2020
@pohly
Copy link
Contributor Author

pohly commented Mar 1, 2022

@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
Copy link
Member

gracenng commented Mar 1, 2022

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
Copy link
Member

gracenng commented Mar 2, 2022

Hi @pohly, does this enhancement need docs?

@gracenng gracenng added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Mar 2, 2022
@pohly
Copy link
Contributor Author

pohly commented Mar 2, 2022

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

@gracenng
Copy link
Member

gracenng commented Mar 15, 2022

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:

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

@gracenng
Copy link
Member

gracenng commented Mar 24, 2022

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

@xing-yang xing-yang modified the milestones: v1.21, v1.24 Mar 29, 2022
@Priyankasaggu11929 Priyankasaggu11929 added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status and removed stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels May 10, 2022
@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented May 10, 2022

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
Copy link

k8s-triage-robot commented Aug 8, 2022

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 8, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Sep 7, 2022

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 7, 2022
@pohly
Copy link
Contributor Author

pohly commented Sep 7, 2022

/close

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

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Sep 7, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Projects
None yet
Development

No branches or pull requests