Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-attach for ebs io1 type #2003

Open
Neophyte12345 opened this issue Apr 11, 2024 · 5 comments
Open

Multi-attach for ebs io1 type #2003

Neophyte12345 opened this issue Apr 11, 2024 · 5 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@Neophyte12345
Copy link

Neophyte12345 commented Apr 11, 2024

Is your feature request related to a problem?/Why is this needed
csi-driver currently only supports multi-attach for io2, however io2 is not available in us-gov-west-1 which limits the use of the csi-driver in certain regions.

https://github.com/kubernetes-sigs/aws-ebs-csi-driver/pull/1799/files#diff-71909558cff6a715e6ba7728d820e0605ec9dc7f28562ea0fc90004762d4901eR10

/feature

Describe the solution you'd like in detail
csi-driver to support provisioning of storage with multi-attach for io1

Describe alternatives you've considered
N/A

Additional context

https://docs.aws.amazon.com/ebs/latest/userguide/ebs-volumes-multi.html

@torredil
Copy link
Member

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 11, 2024
@ksliu58
Copy link

ksliu58 commented Jun 24, 2024

@Neophyte12345 Can you share your use case details requiring multi-attach with io1/io2 volumes?

@Neophyte12345
Copy link
Author

@ksliu58 I guess the use case is for gov-cloud users who deploy their workloads in regions that do not offer ebs io2 type. Would be nice to enable the csi-driver to be able to provision ebs io1 with multi-attach capability enabled at provisioning. We have certain apps that require shared ebs volumes to be attached across nodes.

@ksliu58
Copy link

ksliu58 commented Jun 24, 2024

Sorry, I should be more specific. Multi-attach is a nuanced feature, because you will need IO fencing to protect against data corruption. I am curious of your use case that why it requires the volume to be simultaneously accessed by more than 1 node? What type of application will you be running? Do they operate as read/write many access mode?

@Neophyte12345
Copy link
Author

@ksliu58 The application in question is polyspace access which deploys 2 pods that need a shared volume. 1 is an web server pod and the other is an etl pod which share a volume. We did implement podaffinity to have the pods co-run on the same node to circumvented some of the limitations but thought it would be nice to have a multi-attach ebs volume capability regardless of the node they get scheduled on because sometimes the nodes are not big enough to support all the pods based on resources and type. They operate using access mode RWO. Hope this helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants