search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.46k stars 1.49k forks source link

Add storage capacity scoring #4049

Open cupnes opened 1 year ago

cupnes commented 1 year ago

Enhancement Description

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

cupnes commented 1 year ago

/sig storage

xing-yang commented 1 year ago

Confirmed with @cupnes that this feature is not targeting alpha in 1.28.

k8s-triage-robot commented 10 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale

cupnes commented 10 months ago

The is under review at #4042. /remove-lifecycle stale

k8s-triage-robot commented 7 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale

cupnes commented 7 months ago

/remove-lifecycle stale

k8s-triage-robot commented 4 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale

xing-yang commented 4 months ago

/remove-lifecycle stale

xing-yang commented 2 months ago

/milestone v1.32

dipesh-rawat commented 2 months ago

Hello @cupnes 👋, v1.32 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage alpha for v1.32 (correct me, if otherwise)

Here's where this enhancement currently stands:

For this KEP, we would need to update the following:

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

cupnes commented 2 months ago

@dipesh-rawat I have completed the tasks outlined in this document and am currently waiting for the PRR review.

If you anticipate missing enhancements freeze, you can file an exception request in advance.

I understood. Thank you.

cupnes commented 2 months ago

@dipesh-rawat Since it seems that the PRR for this enhancement will not be completed by the PRR Freeze deadline, I will stop aiming for the alpha stage of v1.32. Please remove this enhancement from the list of enhancements for v1.32.

xing-yang commented 1 month ago

Hi @cupnes , the 10/3 PRR deadline is for the PRR section to be filled out and ready to review. So you still have until 10/10, the KEP freeze deadline, for the PRR section to be approved.

cupnes commented 1 month ago

@xing-yang Thank you for the information. I've changed it back to 1.32.

@dipesh-rawat As stated above, this KEP is targeted to 1.32.

dipesh-rawat commented 1 month ago

Hi @cupnes 👋, v1.32 Enhancements team here.

Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

The current status of this enhancement is marked as at risk for enhancement freeze. There are a few requirements mentioned in the comment https://github.com/kubernetes/enhancements/issues/4049#issuecomment-2372512577 that still need to be completed.

It looks like PR https://github.com/kubernetes/enhancements/pull/4042 will address most of these issues. The PR https://github.com/kubernetes/enhancements/pull/4042 needs to be merged before the enhancements freeze.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

cupnes commented 1 month ago

@dipesh-rawat Thank you for your message.

PR #4042 is currently in a status of awaiting review. I have informed the reviewers that I would like to proceed with merging it if there are no issues, and have requested them to add the necessary labels.

dipesh-rawat commented 1 month ago

Hello @cupnes 👋, v1.32 Enhancements team here,

Now that PR https://github.com/kubernetes/enhancements/pull/4042 has been merged, all the KEP requirements are in place and merged into k/enhancements.

Before the enhancement freeze, it would be appreciated if following nits could be addressed:

Aside from the minor nits mentioned above, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is now marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

cupnes commented 1 month ago

@dipesh-rawat Thank you for checking. I have addressed it!

rashansmith commented 1 month ago

Hello @cupnes 👋 from the v1.32 Communications Team! We'd love for you to consider writing a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog see the blog contribution guidelines.

rdalbuquerque commented 1 month ago

Hello @cupnes :wave:, 1.32 Docs Shadow here. Does this enhancement work planned for 1.32 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!

cupnes commented 1 month ago

@rashansmith Thank you for your message. Yes, I will write the feature blog. First, I will create a placeholder PR with temporary content in the kubernetes/website repository by October 30th.

cupnes commented 1 month ago

@rdalbuquerque Thank you for your message. I understood. First, I will open a PR against the dev-1.32 branch in the kubernetes/website following these steps.

cupnes commented 1 month ago

@rdalbuquerque I opened the following PR against the dev-1.32 branch. https://github.com/kubernetes/website/pull/48382

BenTheElder commented 1 month ago

/retitle Add storage capacity scoring [It is a KEP by being an issue in this repo we don't need KEP in the title 😅 ]

cupnes commented 1 month ago

@rashansmith I created placeholder PR for blog. https://github.com/kubernetes/website/pull/48416

dipesh-rawat commented 1 month ago

Hey again @cupnes 👋 v1.32 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024 .

Here's where this enhancement currently stands:

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

Additionally, please let me know if there are any other PRs in k/k not listed in the description or linked with this GitHub issue that we should track for this KEP, so that we can maintain accurate status.

The status of this enhancement is marked as at risk for code freeze.

If you anticipate missing code freeze, you can file an exception request in advance. Thank you!

cupnes commented 1 month ago

@dipesh-rawat Thank you for your message. I updated this issue's description.

dipesh-rawat commented 3 weeks ago

Hey again @cupnes 👋, v1.32 Enhancements team here,

Just a quick friendly reminder as we approach code freeze in few days, at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024 .

The current status of this enhancement is marked as at risk for code freeze. There are a few requirements mentioned in the comment https://github.com/kubernetes/enhancements/issues/4049#issuecomment-2425315322 that still need to be completed.

If you anticipate missing code freeze, you can file an exception request in advance.

cupnes commented 2 weeks ago

@xing-yang @dipesh-rawat The following PR to k/k for this KEP will not be ready by the code freeze. Therefore, please skip the alpha for this KEP at version 1.32. https://github.com/kubernetes/kubernetes/pull/128184

cupnes commented 2 weeks ago

@rdalbuquerque As mentioned in the above comment, the PR to k/k will not be ready by the code freeze, so the alpha of this KEP will skip version 1.32. Therefore, I will close the following PR that was opened against the dev-1.32 branch of the k/website repository. https://github.com/kubernetes/website/pull/48382

cupnes commented 2 weeks ago

@rashansmith As mentioned in the above comment, this KEP will skip version 1.32. Could I write the feature blog on version 1.33?

dipesh-rawat commented 2 weeks ago

Hello @cupnes 👋 v1.32 Enhancements team here,

Unfortunately, the implementation (code related) PR(s) associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.32 milestone.

If you still wish to progress this enhancement in v1.32, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

/label tracked/no /remove-label tracked/yes /milestone clear

cupnes commented 1 week ago

@rashansmith https://github.com/kubernetes/enhancements/issues/4049#issuecomment-2463545002

Could I write the feature blog on version 1.33?

Regarding this matter, is it all right for me to expect to have the opportunity to write the feature blog for version 1.33? If so, I would like to start preparing early.