aws-ebs-csi-driver icon indicating copy to clipboard operation
aws-ebs-csi-driver copied to clipboard

[Feature] Support initialization of EBS volumes created from Snapshots

Open aaroniscode opened this issue 4 years ago • 8 comments

Is your feature request related to a problem? Please describe. From EBS Documentation (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-initialize.html) For volumes that were created from snapshots, the storage blocks must be pulled down from Amazon S3 and written to the volume before you can access them. This preliminary action takes time and can cause a significant increase in the latency of I/O operations the first time each block is accessed. Volume performance is achieved after all blocks have been downloaded and written to the volume.

The solutions in the documentation aren't compatible with storage assigned to pods. The instructions say "Use the dd or fio utilities to read all of the blocks on the device." However, the block device is not available to the Pod.

Describe the solution you'd like in detail Would like the CSI Driver mechanism to initialize the EBS volume to increase performance of data from snapshot volumes.

Describe alternatives you've considered Not aware of any known alternatives besides migrating workload from EKS to EC2.

Additional context None.

aaroniscode avatar Oct 25 '21 15:10 aaroniscode

/kind feature

gtxu avatar Oct 26 '21 20:10 gtxu

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Jan 24 '22 21:01 k8s-triage-robot

/remove-lifecycle stale

aaroniscode avatar Jan 29 '22 21:01 aaroniscode

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Apr 29 '22 22:04 k8s-triage-robot

/remove-lifecycle stale

aaroniscode avatar Apr 29 '22 23:04 aaroniscode

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Jul 29 '22 00:07 k8s-triage-robot

/remove-lifecycle stale

aaroniscode avatar Jul 29 '22 16:07 aaroniscode

Similar request was open to add support for EBS Fast Snapshot Restore on the ebs csi driver, issue #869 Linking here for tracking.

abencomoc avatar Aug 31 '22 13:08 abencomoc

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Nov 29 '22 13:11 k8s-triage-robot

/remove-lifecycle stale

aaroniscode avatar Nov 29 '22 16:11 aaroniscode

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 avatar Feb 27 '23 17:02 k8s-triage-robot

/remove-lifecycle stale

aaroniscode avatar Feb 28 '23 00:02 aaroniscode