/sig storage

Hi @RaunakShah ! 1.24 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd. This enhancements is targeting alpha for 1.24, is that correct?.
Here’s where this enhancement currently stands:

• Updated KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for this release with latest-milestone: 1.24
• KEP has a test plan section filled out.
• KEP has up to date graduation criteria.
• KEP has a production readiness review that has been completed and merged into k/enhancements.

The status of this enhancement is track as at risk
Thanks!

/milestone v1.24

@gracenng Yes, this is targeting Alpha in 1.24.

Hi @RaunakShah , 1.24 Enhancements Team here.

Reaching out as we're less than a week away from Enhancement Freeze on Thursday, February 3rd.
Updated some points on the check list above, let me know if I missed anything.
I'm monitoring #3151 and current status is at risk

All good for 1.24 Enhancements Freeze

@gracenng Should this have a Tracked/Yes label?

Hi @xing-yang & @RaunakShah, 1.24 Docs shadow here. 👋

This enhancement is marked as Needs Docs for the 1.24 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.24 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 31st March 2022, 18:00 PDT.

Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you! 🙌

Hi @RaunakShah 1.24 Enhancements Team here,

With Code Freeze approaching on 18:00 PDT Tuesday March 29th 2022, the enhancement status is at risk as there is no linked k/k PR. Kindly list them in this issue. Thanks!

PRs are submitted here:
kubernetes-csi/external-snapshotter#665
kubernetes-csi/external-snapshotter#670

@gracenng It might be better to label this feature as "tracked/out-of-tree" as all the code changes are out-of-tree.

All good for Code Freeze!

Hi @RaunakShah, reminder that tomorrow (April 5th) is the deadline for 1.24 Docs Ready for Review.

Please open a PR (and link it back here), push your docs content for this enhancement, and remove the work-in-progress label when ready for review.

We have a tight turnaround to getting docs reviewed and approved for the release, and we’re hoping to have all docs in for review by tomorrow. Thank you!

Here's the doc PR: kubernetes/website#32673

@nate-double-u @xing-yang I've removed the WIP label from the doc PR.

This enhancement proposal mentions the annotation snapshot.storage.kubernetes.io/allowVolumeModeChange. Would it be possible to deprecate that in favor of a more conventional snapshot.storage.kubernetes.io/allow-volume-mode-change?

This enhancement proposal mentions the annotation snapshot.storage.kubernetes.io/allowVolumeModeChange. Would it be possible to deprecate that in favor of a more conventional snapshot.storage.kubernetes.io/allow-volume-mode-change?

We could do that in 1.25.

A note for when this KEP goes to beta (targeting v1.25): the documentation that was added in v1.24 needs to be updated.

/milestone clear

Thank you @RaunakShah ! This enhancement is ready to be traced for graduation to beta in v1.27.

/label tracked/yes
/remove-label tracked/no

@RaunakShah befora graduating to GA, please update the KEP, the new flag is in external-provisioner and snapshot-controller, not external-snapshotter sidecar:

In addition, there could be version skew between the external-provisioner (shipped by a CSI driver vendor) and snapshot-controller (shipped by Kubernetes vendor). I'd appreciate a little more detail in Version skew strategy chapter, now it says it's OK, but it does not say how do we achieve that. What exactly happens when there is new a external-provisioner with old snapshot-controller.

Hi @RaunakShah 👋,

Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.

• Update generated code for SourceVolumeMode field in VolumeSnapshotContents kubernetes-csi/external-snapshotter#665
• Update snapshotter and client modules kubernetes-csi/external-snapshotter#670

For this enhancement, it looks like all linked PRs are merged.

Please let me know what other PRs in k/k I should be tracking for this KEP.

As always, we are here to help should questions come up. Thanks!

Hi @fsmunoz, all code PRs are merged. Just docs/blog remaining. Thanks!

Hello @RaunakShah 👋, Enhancements team here.

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

This enhancement is targeting for stage stable for v1.30 (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: 1.30.
• 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).

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

• The production readiness review should be completed. There is one unanswered question
• Make sure the PR with the information get merged before enhancement freeze, I just found this PR.

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!

@pnbrown The KEP PR is merged. Please let us know if anything is missing. Thanks!
cc @RaunakShah

@xing-yang Thank you. I've marked that complete.

There is still one question on the readiness survey that is not answered:

https://github.com/kubernetes/enhancements/blob/42fe9143b211db01ed7e6e636a4e73ac2f77ae0a/keps/sig-storage/3141-prevent-volume-mode-conversion/README.md#what-are-other-known-failure-modes

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

Hello @RaunakShah, 👋 1.30 Docs Shadow here.
Does this enhancement work planned for 1.30 require any new docs or modifications to existing docs?
If so, please follow the steps here to open a PR against the dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, February 22nd, 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!

Hi @RaunakShah ,

👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!

We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.

To opt in, you need to open a Feature Blog placeholder PR against the website repository.
The placeholder PR deadline is 27th February, 2024.
Here's the 1.30 Release Calendar

@Princesso Here is the placeholder PR for the doc updates - kubernetes/website#45262
@a-mccarthy Here is the placeholder PR for the blog - kubernetes/website#45261

Hey again @RaunakShah 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 .

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

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!

@RaunakShah, Enhancements team here!
As this enhancement is targeting stable for this release, may you please update the status field in the kep.yaml file to implemented as the code PRs are merged and the feature gates are removed.

https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/3141-prevent-volume-mode-conversion/kep.yaml

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.

Hi @pnbrown, the only tickets remaining for this KEP are documentation and blog related. There are no other code changes that need to go in.

As this enhancement is targeting stable for this release, may you please update the status field in the kep.yaml file to implemented as the code PRs are merged and the feature gates are removed.

Sure will do!

@RaunakShah, looks like the links for the blog and docs placeholder PRs got reversed in your comment above. The correct links are below:

@Princesso Here is the placeholder PR for the doc updates - kubernetes/website#45261
@a-mccarthy Here is the placeholder PR for the blog - kubernetes/website#45262

Please note some important deadlines for comms and docs

• from @Princesso here: Hello @RaunakShah 👋 please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before Tuesday March 12th 2024 18:00 PST. Thank you!
• Blog ready for review deadline is March 22, 2024

Please reach out if you have any questions!