Add docs for migration ebs

[nikolasj]

Need documentation with examples on how to transfer data from ebs unencrypted to encrypted.

[hanyuel]

Hi @nikolasj , thanks for opening the issue.
You cannot directly encrypt existing unencrypted volumes or snapshots. However, you can create encrypted volumes or snapshots from unencrypted volumes or snapshots.
See the EBS documentation here: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html#encryption-parameters

[nikolasj]

Hi @hanyuel!
Thank you. I understand how to encrypt a volume. But how to transfer data to this new encrypted EBS?
How do I specify that the new encrypted volume be used?
Can this only be done using Static Provisioning? Or are there options with Dynamic Provisioning?

If I encrypt the snapshot. Then detach and attach a new snapshot, won't the ebs controller scold? He manages ebs himself.

[makarov-roman]

Hi @hanyuel ,
It feels like ebs-csi driver is the part of EKS ecosystem which should implement automatic migration for SC and encryption.
e.g. gp2<>gp3. encrypted <> unencrypted.
afaik there is no automatic way to do so, and it's a problem when you have hundreds of volumes.
I would appreciate your feedback.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[AndrewSirenko]

/remove-lifecycle rotten