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

Manually test PVC CSI snapshot backup/restore in AWS #10211

Open
Tracked by #11476
jenting opened this issue May 24, 2022 · 3 comments
Open
Tracked by #11476

Manually test PVC CSI snapshot backup/restore in AWS #10211

jenting opened this issue May 24, 2022 · 3 comments
Labels
meta: never-stale This issue can never become stale team: workspace Issue belongs to the Workspace team

Comments

@jenting
Copy link
Contributor

jenting commented May 24, 2022

Is your feature request related to a problem? Please describe

Test CSI snapshotter in AWS (follow the self-hosted team guide to deploy to AWS), installed with corresponding AWS CSI driver.
To see if the PVC snapshot/backup works good or not, and if the PVC mount time is slow or not.

Describe the behaviour you'd like

Having a manually test the CSI snapshotter in AWS to see if it's works well or not.

Describe alternatives you've considered

None

Additional context

#7901

@jenting
Copy link
Contributor Author

jenting commented Jul 6, 2022

We could use this PR to bootstrap a EKS cluster for testing.

@jenting jenting moved this to In Progress in 🌌 Workspace Team Jul 11, 2022
@jenting
Copy link
Contributor Author

jenting commented Jul 11, 2022

I use this folder to bootstrap an EKS cluster and follow the notion doc Getting started with self hosted - AWS.

I could bootstrap the AWS EKS cluster, install the snapshotter CRD and snapshot controller, and aws-ebs-csi-driver.

When requesting the volume from PVC, however, I lack permission for it. Ref to https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/b9d3118/docs/install.md#installation-1.
So, I'm asking Mo to let me access the AWS console to configure the IAM role policy.

@stale
Copy link

stale bot commented Oct 12, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@jenting jenting added the meta: never-stale This issue can never become stale label Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: never-stale This issue can never become stale team: workspace Issue belongs to the Workspace team
Projects
None yet
Development

No branches or pull requests

1 participant