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

Kubernetes VolumeAttributesClass ModifyVolume #3751

Open
17 of 20 tasks
sunnylovestiramisu opened this issue Jan 18, 2023 · 59 comments
Open
17 of 20 tasks

Kubernetes VolumeAttributesClass ModifyVolume #3751

sunnylovestiramisu opened this issue Jan 18, 2023 · 59 comments
Assignees
Labels
sig/storage Categorizes an issue or PR as relevant to SIG Storage. 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
Milestone

Comments

@sunnylovestiramisu
Copy link
Contributor

sunnylovestiramisu commented Jan 18, 2023

Enhancement Description

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

@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 18, 2023
@sunnylovestiramisu
Copy link
Contributor Author

/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 18, 2023
@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue 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 Apr 25, 2023
@sunnylovestiramisu
Copy link
Contributor Author

/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 25, 2023
@xing-yang xing-yang added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status lead-opted-in Denotes that an issue has been opted in to a release labels May 22, 2023
@salehsedghpour
Copy link

Hello @sunnylovestiramisu 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 01:00 UTC Friday, 16th June 2023.

This enhancement is targeting for stage alpha for 1.28 (correct me, if otherwise)

Here's where this enhancement currently stands:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for latest-milestone: 1.28
  • KEP readme has a updated detailed test plan section filled out
  • KEP readme has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

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

  • Update status to implementable in kep.yaml
  • Add the test plan in the readme file
  • Address questions inside the Production Readiness Review Questionnaire

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

@xing-yang xing-yang added this to the v1.28 milestone May 27, 2023
@sunnylovestiramisu sunnylovestiramisu changed the title Kubernetes Volume Provisioned IO Kubernetes VolumePerformanceClass ModifyVolume May 31, 2023
@xing-yang xing-yang removed the lead-opted-in Denotes that an issue has been opted in to a release label Jun 1, 2023
@xing-yang xing-yang removed this from the v1.28 milestone Jun 1, 2023
@Atharva-Shinde Atharva-Shinde added this to the v1.28 milestone Jun 2, 2023
@xing-yang xing-yang added the lead-opted-in Denotes that an issue has been opted in to a release label Jun 2, 2023
@salehsedghpour
Copy link

Hi @sunnylovestiramisu 👋, just checking in before the enhancements freeze on 01:00 UTC Friday, 16th June 2023.

The status for this enhancement is at risk.

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

  • Update status to implementable in kep.yaml
  • Add the test plan in the readme file
  • Address questions inside the Production Readiness Review Questionnaire

Let me know if I missed anything. Thanks!

@salehsedghpour salehsedghpour moved this from At Risk to Tracked in 1.28 Enhancements Tracking Jun 15, 2023
@xing-yang xing-yang changed the title Kubernetes VolumePerformanceClass ModifyVolume Kubernetes VolumeAttributesClass ModifyVolume Jun 20, 2023
@AdminTurnedDevOps
Copy link

Hey @sunnylovestiramisu

1.28 Docs Shadow here.

Does this enhancement work planned for 1.28 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.28 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

@sunnylovestiramisu
Copy link
Contributor Author

@AdminTurnedDevOps I think we just need a placeholder PR so that the docs team can add it to tracking. I will follow the instructions, thanks!

@carlory
Copy link
Member

carlory commented Jul 6, 2023

Hi @sunnylovestiramisu , Could you update the link of Kubernetes Enhancement Proposal to https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/3751-volume-attributes-class.

The pr link is difficult for users to learn the content of this KEP.

@dipesh-rawat
Copy link
Member

dipesh-rawat commented Jul 2, 2024

Hey again @sunnylovestiramisu! @mattcary @carlory 👋, 1.31 Enhancements team here,

Just checking in as we approach code freeze at at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

Here's where this enhancement currently stands:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

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):

(Compiled the following list based on the mention of KEP 3751 in the description. Please let me know if there are any PRs listed below that don't require tracking as part of this KEP)

Additionally, please let me know if there are any other PRs in k/k not listed above that we should track for this KEP, so that we can maintain accurate status.

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

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

@dipesh-rawat dipesh-rawat moved this from Tracked for Enhancements Freeze to At Risk for Code Freeze in 1.31 Enhancements Tracking Jul 2, 2024
@dipesh-rawat
Copy link
Member

Hey again @sunnylovestiramisu! @mattcary @carlory 👋, 1.31 Enhancements team here,

Just a quick friendly reminder as we approach code freeze in around two weeks time, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

The current status of this enhancement is marked as at risk for code freeze. There are a few requirements mentioned in the comment #3751 (comment) that still need to be completed.

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

@AndrewSirenko
Copy link
Contributor

Docs modification PR Ready for review: KEP-3751 VolumeAttributeClass Beta Promotion

CC @MaryamTavakkoli, thank you!

@dipesh-rawat
Copy link
Member

Hey again @sunnylovestiramisu! @mattcary @carlory 👋, 1.31 Enhancements team here,

Just a quick friendly reminder as we approach code freeze next week, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

The current status of this enhancement is marked as at risk for code freeze. There are a few requirements mentioned in the comment #3751 (comment) that still need to be completed.

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

@dipesh-rawat
Copy link
Member

Hey again @sunnylovestiramisu! @mattcary @carlory 👋, 1.31 Enhancements team here,

Just a quick friendly reminder as we approach code freeze in less than 2 days, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

The current status of this enhancement is marked as at risk for code freeze. There are a few requirements mentioned in the comment #3751 (comment) that still need to be completed.

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

@AndrewSirenko
Copy link
Contributor

AndrewSirenko commented Jul 23, 2024

Hi @dipesh-rawat, the following PRs should no longer be tracked for Kubernetes v1.31.

See #4765 for more information!

Also:

Is optional for Kubernetes v1.31. If it gets approved in time, that is great, but it should NOT block enhancement promotion to beta!

We will update issue with correct PRs now. Thank you so much for your help/updates!

@dipesh-rawat
Copy link
Member

@AndrewSirenko Thank you for confirming the list of PRs to track for this KEP. I’ve updated the original comment accordingly. I’ll update the status of the KEP on the v1.31 project board closer to the code freeze deadline time later today. Thanks for keeping us informed and ensuring everything is up to date.

@AndrewSirenko
Copy link
Contributor

@dipesh-rawat looks like the final blocking PR is approved by all relevant stakeholders: kubernetes/kubernetes#126145 (comment)

Should merge soon.

Thanks again!

@dipesh-rawat
Copy link
Member

Hey again @AndrewSirenko @mattcary @carlory 👋, 1.31 Enhancements team here,

Everything seems to be in place for this KEP issue now that the following code implementation PRs have been merged.

This enhancement is now marked as tracked for code freeze for the 1.31 Code Freeze!

@tjons
Copy link
Contributor

tjons commented Sep 16, 2024

Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32.

/remove-label lead-opted-in

@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue 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 Dec 15, 2024
@pacoxu
Copy link
Member

pacoxu commented Dec 16, 2024

/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 Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/storage Categorizes an issue or PR as relevant to SIG Storage. 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
Projects
Status: Deferred
Status: Tracked for Code Freeze
Status: Tracked for Doc Freeze
Development

No branches or pull requests