Move Storage Version Migrator in-tree

[enj]

Enhancement Description

• One-line enhancement description (can be used as a release note): Move storage version migrator in-tree
• Kubernetes Enhancement Proposal: KEP
• Discussion Link: 2023-09-06 2023-06-14
• Primary contact (assignee): @nilekhc
• Responsible SIGs: API Machinery
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): v1.30
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-4192: Move Storage Version Migrator in-tree #4240
    • [UPDATE] KEP-4192: Move Storage Version Migrator in-tree #4276
    • chore: updates latest milestone #4673
  • Code (k/k) update PR(s):
    • [Storage Version Migration] feat: implements Storage Version Migration kubernetes#123344
  • Docs (k/website) update PR(s):
    • docs:add docs for StorageVersionMigration v1alpha1 website#45294
• Beta
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
    • svm: set UID and RV on SSA patch to cause conflict on logical create kubernetes#126107
    • [Storage Version Migrator] fix: increases timeout on CRD update check kubernetes#125741
    • [Storage Version Migration] feat: implements Storage Version Migration kubernetes#123344
    • [WIP] [Storage Version Migration] feat: implements Storage Version Migration API in-tree kubernetes#121123
  • Docs (k/website) update(s):

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

[jpbetz]

/label lead-opted-in

[jpbetz]

/milestone v1.29

[k8s-ci-robot]

@jpbetz: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone v1.28

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

@jpbetz: Can not set label lead-opted-in: Must be member in one of these teams: [release-team-enhancements release-team-leads sig-api-machinery-leads sig-apps-leads sig-architecture-leads sig-auth-leads sig-autoscaling-leads sig-cli-leads sig-cloud-provider-leads sig-cluster-lifecycle-leads sig-contributor-experience-leads sig-docs-leads sig-instrumentation-leads sig-k8s-infra-leads sig-multicluster-leads sig-network-leads sig-node-leads sig-release-leads sig-scalability-leads sig-scheduling-leads sig-security-leads sig-storage-leads sig-testing-leads sig-windows-leads]

In response to this:

/label lead-opted-in

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jpbetz]

/label lead-opted-in
(I've added myself to the org team)

[sftim]

I would:
/retitle Move storage version migrator in-tree