@andyzhangx do you plan to target beta for this in 1.20?

yes, here is the detailed plan: kubernetes-sigs/azurefile-csi-driver#115

Hi @andyzhangx

The design doc that you linked for this Enhancement is using an old format, please update to use the current KEP format here: https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template

Also please note that Enhancements Freeze is October 6th and by that time we expect that:

The KEP must be merged in an implementable state (the format you are using has no such state)
The KEP must have test plans (can you specify which need to be done for beta https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/csi-migration.md#testing)
The KEP must have graduation criteria (The schedule is stale and references milestones that has already passed: https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/csi-migration.md#implementation-schedule)

Thanks
Kirsten

Hi @andyzhangx

Enhancements Freeze is October 6th. Can you please respond to the above query and update the doc as requested?

Thanks!
Kirsten

Hi @kikisdeliveryservice, this is the KEP we're using to track all the different csi migration implementations https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/20190129-csi-migration.md

Hi @msau42 I spoke to @palnabarun earlier today and got the background. I marked this tracked and good to go for 1.20 👍

Hey @andyzhangx !

Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates:
Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze

As a reminder, please link all of your k/k PR as well as docs PR to this issue so we can track them.

Thanks so much,

Kendall

Hello @andyzhangx, 1.20 Docs shadow here 👋🏽.
Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th

Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

Hi @andyzhangx
The docs placeholder deadline is almost here. Please make sure to create a placeholder PR against the dev-1.20 branch in the k/website before the deadline

Also, please keep in mind the important upcoming dates:

• Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
• Thursday, Nov 12th: Week 9 - Code Freeze
• Monday, Nov 23rd: Week 11 - Docs PR Ready for Review
  As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track.

Thank you

Hi @andyzhangx

Code Freeze is now in effect. Your PR is still unmerged, with no approvals and has a hold. If you believe this should be in the 1.20 Release, please file an Exception.

Best,
Kirsten

Hi @andyzhangx, 1.21 Enhancements Lead here.
This enhancement has been opt-in for the 1.21 release without a KEP link. However, I was able to locate the CSI migration KEP under sig storage. Could you confirm that https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/625-csi-migration is the correct one that's associated with this issue?

Hi @andyzhangx, 1.21 Enhancements Lead here.
This enhancement has been opt-in for the 1.21 release without a KEP link. However, I was able to locate the CSI migration KEP under sig storage. Could you confirm that https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/625-csi-migration is the correct one that's associated with this issue?

@annajung yes, thanks, we resolved the blocking issue, and Azure file in-tree to CSI driver migration would go beta in 1.21.

Hello @andyzhangx 👋, 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 stable for 1.25 release

Here's where this enhancement currently stands:

• KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable
• KEP has an updated detailed 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.

Referring to above conversations I have noted that the graduation criteria and test-plan is inherited by this parent KEP (correct me if thats not true)

So it looks like for this one, we would need to update the following:

• Please update the Issue description with the correct URL for the Kubernetes Enhancement Proposal
• According to the latest KEP template add a dedicated Design Details section and move the Test plan and Graduation sub-sections under this section
• The KEP needs updating it's Test Plan Section to incorporate more details as stated in the updated detailed test plan
• Update the kep.yaml to reflect the latest milestone & stage information
• Update the production readiness review to move to the stable stage

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!

we are targeting CSI migration GA on 1.25, here is the k/k PR: kubernetes/kubernetes#110458

Moving to 1.26 per comment here: kubernetes/kubernetes#110458 (comment)

Thanks for the clarification ^ @xing-yang. 👍

Hey @andyzhangx @xing-yang 👋
Just for note: Enhancements Freeze is now extended to next week till Thursday June 23, 2022 🚀
So we now have one more week :)

Thanks @Atharva-Shinde! We are still targeting GA in 1.26.

I have set Stable release target 1.26

Hello @andyzhangx 👋, 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 stable for 1.26 (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.26
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

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

• Update the PRR approver file for stage stable
• Update the KEP file for stage and latest-milestone
• After updating, please plan to merge KEP-1885: Update Azure File csi migration #3360 before enhancements freeze

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!

With #3360 merged, this enhancement is now tracked for the v1.26 cycle. Thanks!

Hi @andyzhangx 👋,

Checking in once more as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

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.

For this enhancement, it looks like we'll need a PR to graduate this feature to stable.

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

Hello @andyzhangx ! 👋🏾,

@katmutua 1.26 Release Docs shadow here. This enhancement is marked as ‘Needs Docs’ for 1.26 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9.

Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.
As a reminder, please link all of your docs PR to this issue so we can easily track it.

@andyzhangx are the merged parent enhancement docs sufficient to cover changes made by this enhancement? If so will mark docs as completed and merged.

@andyzhangx are the merged parent enhancement docs sufficient to cover changes made by this enhancement? If so will mark docs as completed and merged.

@katmutua with this PR(kubernetes/kubernetes#113160) merged, I think we could mark as completed and merged.

With kubernetes/kubernetes#113160 merged, I have this marked as tracked for code freeze.

The doc PR for the release 1.26 here
cc: @katmutua

Hi @andyzhangx - since this enhancement has graduated to stable can you please update https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1885-csi-migration-azurefile/kep.yaml setting the status to implemented and then close this issue.
Thanks!

Hi @andyzhangx - since this enhancement has graduated to stable can you please update https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1885-csi-migration-azurefile/kep.yaml setting the status to implemented and then close this issue. Thanks!

@marosset good catch, here is the PR: #3688

close this issue as suggested