KEP-1487: Add csi migration kep for AWS EBS

[Jiawei0227]

• One-line PR description:
  This PR adds csi migration kep for aws-ebs

• Issue link: AWS EBS in-tree to CSI driver migration #1487

• Other comments:

[Jiawei0227]

/cc @msau42 @xing-yang @wongma7 @ehashman

[xing-yang]

/lgtm

[xing-yang]

/milestone v1.24

[msau42]

/lgtm
/approve

[msau42]

/assign @ehashman

[wojtek-t]

@msau42 @ehashman @Jiawei0227 - I'm wondering if (given that I'm approving the PRR for the main CSI migration KEP now to GA and previously Beta), maybe it makes sense to reassign all of these sibling provider-related ones to me too? I'm happy to take them

[Jiawei0227]

@msau42 @ehashman @Jiawei0227 - I'm wondering if (given that I'm approving the PRR for the main CSI migration KEP now to GA and previously Beta), maybe it makes sense to reassign all of these sibling provider-related ones to me too? I'm happy to take them

Thanks a lot! I will reassign them to you!

[Jiawei0227]

/assign @wojtek-t

[ehashman]

@msau42 @ehashman @Jiawei0227 - I'm wondering if (given that I'm approving the PRR for the main CSI migration KEP now to GA and previously Beta), maybe it makes sense to reassign all of these sibling provider-related ones to me too? I'm happy to take them

Ah, I did a bunch of these last release... just looked through one or two but only saw this comment now.

I think that's fine. I also ran through the questionnaire and it generally looked good to me for beta. I did have one concern:

enhancements/keps/sig-storage/625-csi-migration/README.md

Lines 409 to 410 in 6ec5481

	* **What steps should be taken if SLOs are not being met to determine the problem?**
	- Take the CSI driver log, kube-controller-manager log and kubelet log to analyze why the SLOs are not being met. What is the most error status and why is it error.

"Read the logs" isn't really troubleshooting guidance. I'd expect this to indicate what people should specifically be looking for in the logs, and not just suggest that they should check them. :)

[wojtek-t]

"Read the logs" isn't really troubleshooting guidance. I'd expect this to indicate what people should specifically be looking for in the logs, and not just suggest that they should check them. :)

That's a fair point.
@Jiawei0227 - can you please extend that in the main CSI migration kep PRR?

[Jiawei0227]

That's a fair point.
@Jiawei0227 - can you please extend that in the main CSI migration kep PRR?

Sure, I created a PR: #3152. hopefully this provides some debugging process to trouble shoot any potential errors/issues.

[ehashman]

I will leave @wojtek-t as the approver and unassign these PRs. Thanks!

[wojtek-t]

@Jiawei0227 - One minor comment

[msau42]

/hold
@wongma7 to confirm if we want to target 1.24

[wojtek-t]

/lgtm
/approve PRR

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jiawei0227, msau42, wojtek-t

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• keps/prod-readiness/OWNERS [wojtek-t]
• keps/sig-storage/OWNERS [msau42]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[wojtek-t]

@msau42 - should we cancel hold?
If we decide not to proceed later in the cycle, we can always do that. If this will miss the deadline, we won't be able to recover from it.

[msau42]

Yeah sounds good to me.

/hold cancel

[wongma7]

retroactive 👍

thx all.