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

Remove gitRepo volume driver #5040

Open
2 of 6 tasks
vinayakankugoyal opened this issue Jan 14, 2025 · 5 comments
Open
2 of 6 tasks

Remove gitRepo volume driver #5040

vinayakankugoyal opened this issue Jan 14, 2025 · 5 comments
Assignees
Labels
lead-opted-in Denotes that an issue has been opted in to a release 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/yes Denotes an enhancement issue is actively being tracked by the Release Team
Milestone

Comments

@vinayakankugoyal
Copy link
Contributor

vinayakankugoyal commented Jan 14, 2025

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 14, 2025
@xing-yang
Copy link
Contributor

/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 14, 2025
@xing-yang xing-yang added lead-opted-in Denotes that an issue has been opted in to a release and removed sig/storage Categorizes an issue or PR as relevant to SIG Storage. labels Jan 14, 2025
@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 14, 2025
@k8s-ci-robot
Copy link
Contributor

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>
  • /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

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-sigs/prow repository.

@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 and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. lead-opted-in Denotes that an issue has been opted in to a release labels Jan 14, 2025
@xing-yang xing-yang added this to the v1.33 milestone Jan 14, 2025
@xing-yang xing-yang added the sig/storage Categorizes an issue or PR as relevant to SIG Storage. label Jan 14, 2025
@sftim
Copy link
Contributor

sftim commented Jan 17, 2025

/retitle Remove gitRepo volume driver

@k8s-ci-robot k8s-ci-robot changed the title Remove gitRepo volume driver. Remove gitRepo volume driver Jan 17, 2025
@vinayakankugoyal
Copy link
Contributor Author

/assign @vinayakankugoyal

@fykaa
Copy link
Member

fykaa commented Feb 4, 2025

Hello @vinayakankugoyal 👋, v1.33 Enhancements team here.

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

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

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: v.133. 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 submitted a production readiness review request for approval and has a reviewer assigned.
  • KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

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

@fykaa fykaa moved this to Tracked for enhancements freeze in 1.33 Enhancements Tracking Feb 4, 2025
@dipesh-rawat dipesh-rawat added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lead-opted-in Denotes that an issue has been opted in to a release 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/yes Denotes an enhancement issue is actively being tracked by the Release Team
Projects
Status: Tracked for enhancements freeze
Development

No branches or pull requests

6 participants