search

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.

xing-yang commented 2 years ago

/sig storage

xing-yang commented 2 years ago

/wg data-protection

xing-yang commented 2 years ago

/milestone v1.25

jasonbraganza commented 2 years ago

Hello @phuongatemc 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 16, 2022.

For note, This enhancement is targeting for stage alpha for 1.25 (correct me, if otherwise)

Here's where this enhancement currently stands:

Looks like for this one, we would need to update the following:

Open KEP PR https://github.com/kubernetes/enhancements/pull/3367

For note, 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!

jasonbraganza commented 2 years ago

Hello @phuongatemc, @ihcsim 👋, just a quick check-in again, as we approach the 1.25 enhancements freeze.

Please plan to get the above done before enhancements freeze on Thursday, June 16, 2022 at 18:00 PM PT.

For note, the current status of the enhancement is atat-risk. Thank you!

phuongatemc commented 2 years ago

@jasonbraganza I have updated the issue description with the PR https://github.com/kubernetes/enhancements/pull/3367 This is still an work in progress so we don't have the code ready yet but here is our repository https://github.com/phuongatemc/diffsnapcontroller/

jasonbraganza commented 2 years ago

Thank you so much for the updates, @phuongatemc 🙂

Could you please, make the following updates in you open PR https://github.com/kubernetes/enhancements/pull/3367

  1. Update the status from provisional to implementable in the kep.yaml file.
  2. Please update the test plan section, to add the test information in the requested format, as described in the template

Please plan to have the PR merged, before the updated enhancements freeze date on Thursday, June 23, 2022.

ihcsim commented 2 years ago

@jasonbraganza thanks - we added the test plan section yesterday. I thought the KEP must be approved before we can update it to implementable.

jasonbraganza commented 2 years ago

Hello @ihcsim. Just checking in, as we are four days away from the enhancements freeze on Thursday, June 23, 2022 at 18:00 PM PT.

I thought the KEP must be approved before we can update it to implementable.

For a KEP to be tracked in release cycle, it should be marked as implementable.

Kindly plan to have the PR merged by the freeze date.

Please note: the current status of the enhancement is at-risk. Thank you.

Priyankasaggu11929 commented 2 years ago

Hello, 1.25 Enhancements Lead here 👋. With Enhancements Freeze now in effect, this enhancement has not met the criteria for the freeze and has been removed from the milestone.

As a reminder, the criteria for enhancements freeze is:

Feel free to file an exception to add this back to the release. If you plan to do so, please file this as early as possible.

Thanks! /milestone clear

xing-yang commented 2 years ago

/milestone v1.26

Atharva-Shinde commented 2 years ago

Hey @phuongatemc 👋, 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 alpha for 1.26 (correct me, if otherwise)

Here's where this enhancement currently stands:

For this KEP, we would need to:

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

Atharva-Shinde commented 2 years ago

/label tracked/yes

ihcsim commented 2 years ago

/assign @ihcsim

Atharva-Shinde commented 2 years ago

Hello @phuongatemc @ihcsim 👋, just a quick check-in again, as we approach the 1.26 Enhancements freeze.

Please plan to get the action items mentioned in my comment above done before Enhancements freeze on 18:00 PDT on Thursday 6th October 2022 i.e tomorrow

For note, the current status of the enhancement is marked at-risk :)

rhockenbury commented 2 years ago

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 /label tracked/no /remove-label tracked/yes /remove-label lead-opted-in

k8s-triage-robot commented 1 year ago

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

xing-yang commented 1 year ago

/remove-lifecycle stale

Atharva-Shinde commented 1 year ago

Hello @ihcsim @phuongatemc 👋, 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 alpha for 1.27 (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. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

Atharva-Shinde commented 1 year ago

Hey again @ihcsim @phuongatemc
Please try to get the KEP PR #3367 (addressing the changes mentioned above), merged before tomorrow's Enhancement Freeze :) The status of this enhancement is still marked as at risk

xing-yang commented 1 year ago

Hi @Atharva-Shinde, this KEP https://github.com/kubernetes/enhancements/pull/3367 is not merged yet. We are still going through design discussions. Thanks.

Atharva-Shinde commented 1 year ago

Oops my bad @xing-yang thank you for notifying I'll delete my comment and I have changed the status back to at risk

marosset commented 1 year ago

Unfortunately, this exception hasn't satisfied all of the requirements by the v1.27 code freeze and will be removed from the milestone.

If you feel it is important to include this exception in v1.27 please consider filing an exception as outlined at https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

k8s-triage-robot commented 1 year ago

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

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

xing-yang commented 1 year ago

/remove-lifecycle stale

xing-yang commented 1 year ago

/milestone v1.29

sreeram-venkitesh commented 1 year ago

Hello @phuongatemc @ihcsim 👋, v1.29 Enhancements team here.

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

This enhancement is targeting for stage `alpha for v1.29 (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. Thank you!

sreeram-venkitesh commented 1 year ago

Hi @phuongatemc @ihcsim, checking in once more as we approach the 1.29 enhancement freeze deadline on 01:00 UTC Friday, 6th October 2023. The status of this enhancement is marked as at risk. It looks like https://github.com/kubernetes/enhancements/pull/4082 will address most of the requirements. Please make sure that the changes are merged in time. Let me know if I missed anything. Thanks!

npolshakova commented 1 year ago

Hello 👋, 1.29 Enhancements Lead here. Unfortunately, this enhancement did not meet requirements for v1.29 enhancements freeze. Feel free to file an exception to add this back to the release tracking process. Thanks!

https://github.com/kubernetes/enhancements/pull/4082 still needs SIG approval to complete the enhancement freeze requirements.

/milestone clear

xing-yang commented 1 year ago

@npolshakova Can you please add a label "tracked/out-of-tree"? The implementation for this feature is completely out-of-tree.

salehsedghpour commented 9 months ago

/remove-label lead-opted-in

tjons commented 9 months ago

Hello @phuongatemc 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on Friday, February 9th, 2024 at 02:00 UTC.

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

Here's where this enhancement currently stands:

For this KEP, we would just need to complete 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. Thank you!

xing-yang commented 8 months ago

@tjons Thanks for the reminder! I think that we won't be able to merge the KEP tomorrow. Since the development is out-of-tree, we'll continue to work on it.

salehsedghpour commented 8 months ago

/milestone clear

k8s-triage-robot commented 5 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

xing-yang commented 5 months ago

/remove-lifecycle stale

sreeram-venkitesh commented 5 months ago

Hello @phuongatemc @xing-yang 👋, 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:

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

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. Please let me know if you have any questions! Thank you!

PrasadG193 commented 4 months ago

Hey @sreeram-venkitesh, We've changed the milestone to v1.31. For changing the status to implementable, I just wanted to confirm if this has to be changed only after merging the KEP PR.

MaryamTavakkoli commented 4 months ago

Hello @ihcsim and @phuongatemc 👋, 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 commented 4 months ago

@PrasadG193 You can mark the KEP as implementable if your PRR review is done and approved. I can see that you've done this in your PR. This change can be made along with the KEP PR if I'm not wrong, since the PRR team would be reviewing the KEP PR before merging it anyway.

I can see that the kep.yaml says implementable here, which is what we want. Please make sure to get this PR merged before the enhancements freeze on 2 AM UTC on Friday June 14th!

PrasadG193 commented 4 months ago

@sreeram-venkitesh the KEP PR has been merged. Please let us know if anything else needs to be done. Thank you!

sreeram-venkitesh commented 4 months ago

@PrasadG193 Thanks for the response! Marking this KEP as tracked for enhancements freeze!

carlbraganza commented 4 months ago

Hello @ihcsim and @phuongatemc 👋, 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!

We expect the documentation to be out-of-tree in the https://github.com/kubernetes-csi/docs repo - they will become visible in (https://kubernetes-csi.github.io/docs. This will be done after the sidecar is developed.

edithturn commented 4 months ago

Hello @ihcsim and @phuongatemc!

👋 from the v1.31 Communications Team!

We'd love for you to opt in to write 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 3rd July, 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.

MaryamTavakkoli commented 4 months ago

Hello @ihcsim and @phuongatemc 👋, 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!

We expect the documentation to be out-of-tree in the https://github.com/kubernetes-csi/docs repo - they will become visible in (https://kubernetes-csi.github.io/docs. This will be done after the sidecar is developed.

@carlbraganza Please open a placeholder PR as well.

MaryamTavakkoli commented 4 months ago

@PrasadG193 @carlbraganza @ihcsim @phuongatemc Please remember that tomorrow, Thursday, June 27, 2024, 18:00 PDT, is the deadline for the Draft PR.

xing-yang commented 4 months ago

@MaryamTavakkoli I see that @carlbraganza has a response regarding the doc PR here: https://github.com/kubernetes/enhancements/issues/3314#issuecomment-2166478090

PrasadG193 commented 4 months ago

@MaryamTavakkoli @xing-yang I've created a placeholder PR https://github.com/kubernetes-csi/docs/pull/601

edithturn commented 4 months ago

Hello @ihcsim and @phuongatemc!

👋 from the v1.31 Communications Team!

We'd love for you to opt in to write 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 3rd July, 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.

Hello @ihcsim , @phuongatemc 👋!

Just a friendly reminder: if you need to open a Feature Blog placeholder PR against the website repository, please go ahead and do so. If you have any questions or need any help, feel free to reach out! For more information about writing a blog, check out the blog contribution guidelines.

Remember, the deadline for this is coming up soon: Wednesday, July 03, 2024, at 18:00 PDT.

Thank you!! Edith

PrasadG193 commented 4 months ago

@edithturn we have created a block placeholder PR https://github.com/kubernetes/website/pull/47058