KEP-1885: Update Azure File csi migration (kubernetes#3360)

* KEP-1885: Update Azure File csi migration test plan

revert kep.yaml

fix

fix comments

* set as stable

* use beta version

* Update 1885.yaml

* Update README.md

* Update kep.yaml

* Update kep.yaml

Author: andyzhangx

keps/prod-readiness/sig-storage/1885.yaml

@@ -1,3 +1,5 @@
 kep-number: 1885
 beta:
-  approver: "@wojtek-t"
+  approver: "@wojtek-t"
+stable:
+  approver: "@wojtek-t"

keps/sig-storage/1885-csi-migration-azurefile/README.md

@@ -6,6 +6,12 @@
 - [Summary](#summary)
   - [New Feature Gates](#new-feature-gates)
 - [Production Readiness Review Questionnaire](#production-readiness-review-questionnaire)
+- [Design Details](#design-details)
+  - [Test Plan](#test-plan)
+      - [Prerequisite testing updates](#prerequisite-testing-updates)
+      - [Unit tests](#unit-tests)
+      - [Integration tests](#integration-tests)
+      - [e2e tests](#e2e-tests)
 - [Implementation History](#implementation-history)
 <!-- /toc -->
 
@@ -40,6 +46,36 @@ used as as described in its parent KEP. For all other contents, please refer to
 
 Please refer to the [CSI Migration Production Readiness Review Questionnaire](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/625-csi-migration#production-readiness-review-questionnaire).
 
+## Design Details
+### Test Plan
+
+[X] I/we understand the owners of the involved components may require updates to
+existing tests to make this code solid enough prior to committing the changes necessary
+to implement this enhancement.
+
+##### Prerequisite testing updates
+
+No additional tests are needed, rather the issue is orchestrating CSI driver
+deployment for prow jobs. This has been complicated by the cloud provider
+extraction work, which no longer permits cloud provider specific orchestration
+in the k/k repository. This means that it is not possible to run any test for
+AzureFile in k/k. All such tests have been moved to the [Azure File CSI Driver repo](https://github.com/kubernetes-sigs/azurefile-csi-driver).
+
+##### Unit tests
+
+https://github.com/kubernetes/csi-translation-lib/blob/master/plugins/azure_file_test.go
+
+##### Integration tests
+
+N/A
+
+##### e2e tests
+
+Support for tests after AzureFile migration have been [added to
+azurefile-csi-driver](https://github.com/kubernetes-sigs/azurefile-csi-driver/tree/master/test/e2e).
+
+The e2e tests are now covered in [azurefile-csi-driver-e2e-migration](https://testgrid.k8s.io/provider-azure-azurefile-csi-driver#pr-azurefile-csi-driver-e2e-migration).
+
 ## Implementation History
 
 Major milestones in the life cycle of a KEP should be tracked in `Implementation History`.
@@ -56,3 +92,6 @@ Major milestones for Azure File in-tree plugin CSI migration:
 
 - 1.24
   - AzureFile CSI migration to Beta, on by default
+
+- 1.26
+  - AzureFile CSI migration to GA, on by default

keps/sig-storage/1885-csi-migration-azurefile/kep.yaml

@@ -20,17 +20,18 @@ see-also:
 replaces:
 
 # The target maturity stage in the current dev cycle for this KEP.
-stage: beta
+stage: stable
 
 # The most recent milestone for which work toward delivery of this KEP has been
 # done. This can be the current (upcoming) milestone, if it is being actively
 # worked on.
-latest-milestone: "v1.24"
+latest-milestone: "v1.26"
 
 # The milestone at which this feature was, or is targeted to be, at each stage.
 milestone:
   alpha: "v1.15"
   beta: "v1.21"
+  stable: "v1.26"
 
 # The following PRR answers are required at alpha release
 # List the feature gate name and the components for which it must be enabled