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
VolumeGroupSnapshot #3476
Comments
/sig storage |
/milestone v1.26 |
Hello @xing-yang 👋, 1.26 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as |
Quick reminder - Enhancement freeze is 2 days away. If you are still looking to get this enhancement into v1.26, please plan to make the updates to the kep.yaml, and README and get the PR merged. |
@ruheenaansari34 Thanks for the reminder! I updated the KEP and moved test plan and graduation criteria under design details section. |
@xing-yang Thank you. I've re-assessed it and looks like we still need
Specifically, this statement:
Once the PR is merged with the above change, the enhancements freeze requirements will be fulfilled. |
@ruheenaansari34 I've updated the KEP PR with the owner's acknowledgment and also moved "Alternatives" after "Implementation History". PTAL. Thanks. |
Thank you. Please ensure the PR is merged before enhancements freeze at 18:00 PDT today and that will fulfill requirements. |
Hi @ruheenaansari34, we need more time to finalize the design details so the KEP won't be merged today. Since the implementation is completely out-of-tree, we will continue to work on it. When you remove the |
Hello 👋, 1.26 Enhancements Lead here. Unfortunately, this enhancement did not meet requirements for enhancements freeze. If you still wish to progress this enhancement in v1.26, please file an exception request. Thanks! /milestone clear |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Hello @xing-yang 👋, Enhancements team here. Just checking in as we approach Enhancements freeze on 18:00 PDT Thursday 9th February 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as |
The new question is not needed for alpha but would be nice to have. The PRR approval is still in place from last cycle, and I went through commit-by-commit and all the answers on the updated KEP look consistent with the previous discussions. So PRR is approved. |
@Atharva-Shinde I updated the PRR checkbox above |
Hey again @xing-yang |
@Atharva-Shinde The KEP is merged. |
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 |
Hi @xing-yang, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release. Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release. Please feel free to reach out with any questions. Thanks! |
Hey @xing-yang 👋 Enhancements team here, |
Hi @Atharva-Shinde, all code development are out of tree in this repo: https://github.com/kubernetes-csi/external-snapshotter. So we don't need to follow the k/k code freeze deadline. It already has a "tracked/out-of-tree" label. Thanks! |
Hi @LukeMwila, since all the code will be developed out of tree, the docs will also be out of tree here: https://kubernetes-csi.github.io/docs/. So I think we don't need to add docs in k/website. Thanks! |
/remove-label tracked/no |
Enhancement Description
Introduce a VolumeGroupSnapshot API to take a snapshot of multiple volumes together.
k/enhancements
) update PR(s): KEP-3476: Add Volume Group Snapshot KEP #1551k/k
) update PR(s):k/website
) update PR(s): Placeholder blog PR: Add post-release blog article about Volume Group Snapshot alpha website#39415Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: