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

In-tree volume plugins remove dynamic provisioning support #4547

Open
4 tasks
carlory opened this issue Mar 14, 2024 · 10 comments
Open
4 tasks

In-tree volume plugins remove dynamic provisioning support #4547

carlory opened this issue Mar 14, 2024 · 10 comments
Labels
sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@carlory
Copy link
Member

carlory commented Mar 14, 2024

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 Mar 14, 2024
@carlory
Copy link
Member Author

carlory commented Mar 14, 2024

/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 Mar 14, 2024
@xing-yang xing-yang added the lead-opted-in Denotes that an issue has been opted in to a release label May 16, 2024
@xing-yang xing-yang added this to the v1.31 milestone May 16, 2024
@sreeram-venkitesh
Copy link
Member

/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Jun 3, 2024
@sreeram-venkitesh
Copy link
Member

Hello @carlory 👋, v1.31 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting for stage alpha for v1.31 (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: v1.31. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
  • KEP readme has up-to-date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline so that the PRR team has enough time to review your KEP before the enhancements freeze.

For this KEP, we need to do the following:

Please get the PRR review done and the KEP files merged before the enhancements freeze!

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

If you anticipate missing enhancements freeze, you can file an exception request in advance. Let me know if you have any questions! Thank you!

@jpbetz jpbetz assigned jpbetz and unassigned jpbetz Jun 5, 2024
@MaryamTavakkoli
Copy link

Hello @carlory 👋, 1.31 Docs Shadow here.
Does this enhancement work planned for 1.31 require any new docs or modifications to existing docs?
If so, please follow the steps here to open a PR against the dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, June 27, 2024, 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release.
Thank you!

@sreeram-venkitesh
Copy link
Member

@carlory Pinging as a reminder that we are approaching the enhancements freeze deadline, which is on this Friday, June 14th!

@jpbetz
Copy link
Contributor

jpbetz commented Jun 11, 2024

PRR reviewer here. I'd like to see this deprecation guarded by a feature gate. I've added some comments.

I'm also curious how much value we get out of this deprecation? Should we be investing in it or would it be better to just mark the feature as forever deprecated and leave it as-is? (cc @msau42 )

@carlory
Copy link
Member Author

carlory commented Jun 13, 2024

@jpbetz @sreeram-venkitesh I appreciate your reminder. I have to postpone it to 1.32 because of a personal issue. I will update the KEP according to the feedback when I have time.

@sreeram-venkitesh
Copy link
Member

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.31 milestone Jun 14, 2024
@sreeram-venkitesh
Copy link
Member

/label tracked/no

@k8s-ci-robot k8s-ci-robot added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Jun 24, 2024
@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-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Sep 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/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
No open projects
Status: Deferred
Development

No branches or pull requests

7 participants