kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.43k stars 1.48k forks source link

CSI Differential Snapshot for Block Volumes #3314

Open phuongatemc opened 2 years ago

phuongatemc commented 2 years ago

Enhancement Description

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

edithturn commented 4 months ago

@edithturn we have created a block placeholder PR kubernetes/website#47058

Thank you @PrasadG193

sreeram-venkitesh commented 3 months ago

Hey again @PrasadG193 @xing-yang 👋 v1.31 Enhancements team here,

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

Here's where this enhancement currently stands:

~For this KEP, since its out of tree, I was not able to find any of the associated PRs. Please let me know which all PRs we should be tracking for code freeze~ and update them in the issue description as well. I'm marking this KEP as At risk for code freeze for now.

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

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks!

PrasadG193 commented 3 months ago

@sreeram-venkitesh The code PRs for this enhancement can be found at - https://github.com/kubernetes-csi/external-snapshot-metadata/pulls. The PRs are getting reviewed and merged to this new repo https://github.com/kubernetes-csi/external-snapshot-metadata

sreeram-venkitesh commented 3 months ago

Thanks @PrasadG193! I see that all the PRs to the repo you linked are merged. Are these all the PRs related to the KEPs or are we expecting more PRs? If that is all, I can mark this KEP as Tracked for code freeze. Please let me know. Also please make sure to update the issue description with the links to the PR.

PrasadG193 commented 3 months ago

@sreeram-venkitesh We are expecting more PRs, the implementation is not complete yet. I don't think we'll be able to complete the implementation by the code freeze deadline you posted - 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

sreeram-venkitesh commented 3 months ago

@PrasadG193 Ah no worries, I will keep this KEP as At risk for code freeze till next week till the code freeze party. Let me know if you have anything!

sreeram-venkitesh commented 3 months ago

@PrasadG193 I see that all the PRs in https://github.com/kubernetes-csi/external-snapshot-metadata/pulls have been merged. Do we have any more PRs that needs to be merged for the v1.31 release?

PrasadG193 commented 3 months ago

@sreeram-venkitesh yes, we are expecting more PRs. The implementation is not complete yet.

sreeram-venkitesh commented 3 months ago

Hello @PrasadG193 👋 v1.31 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.31 milestone.

If you still wish to progress this enhancement in v1.31, 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!

/milestone clear

tjons commented 1 month ago

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

PrasadG193 commented 1 month ago

Hey @tjons, could you please add this for 1.32?

tjons commented 1 month ago

/milestone v1.32

tjons commented 1 month ago

/label lead-opted-in

tjons commented 1 month ago

Hello @PrasadG193 👋, 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 stable for v1.32 (correct me, if otherwise).

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 at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well.

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

PrasadG193 commented 3 weeks ago

Hey @tjons, since the KEP is already merged, are we expected to raise a PR for this change?

tjons commented 3 weeks ago

Hi @PrasadG193 - yes, the KEP status is required to be implementable for the latest-milestone of the current release.

PrasadG193 commented 3 weeks ago

@tjons PTAL at https://github.com/kubernetes/enhancements/pull/4909

tjons commented 3 weeks ago

@PrasadG193 Once that merges, the requirements will be met! Please reach out to reviewers to make sure that the changes merge before enhancements freeze tomorrow evening.

tjons commented 3 weeks ago

With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀

rdalbuquerque commented 2 weeks ago

Hello @PrasadG193 :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!

PrasadG193 commented 1 week ago

@rdalbuquerque I've created a draft PR at - https://github.com/kubernetes/website/pull/48456, please let me know if anything else is needed. Thank you!

wrkode commented 1 week ago

👋 Hi there, William here from v1.32 Comms 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.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

PrasadG193 commented 6 days ago

Hey @wrkode, I've already opened a placeholder PR https://github.com/kubernetes/website/pull/48456, let me know if anything else is needed.

wrkode commented 6 days ago

Hi @PrasadG193, this is enough for now, thanks a million

tjons commented 4 days ago

Hello @PrasadG193 👋, Enhancements team here.

Are there any code changes planned for this KEP in 1.32? If so, please let me know and add them to the issue description. I will mark this KEP as at risk for code freeze until I hear from you.