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

When user uses IRSA in EKS the credential file should not be needed. #6181

Closed
reasonerjt opened this issue Apr 24, 2023 · 2 comments
Closed
Assignees
Labels
Area/Cloud/AWS IAM Issues related to identity and access management
Milestone

Comments

@reasonerjt
Copy link
Contributor

I've verified the functionality around IRSA in #4959 with the credential file provided.

We want to verify the scenario that when the user uses IRSA on EKS he should not need to provide the credential files

There may be some code changes needed in AWS plugin, we should try to close this gap in v1.12 timeframe.

@reasonerjt reasonerjt added Area/Cloud/AWS IAM Issues related to identity and access management labels Apr 24, 2023
@reasonerjt reasonerjt self-assigned this Apr 24, 2023
@reasonerjt reasonerjt added this to the v1.12 milestone Apr 24, 2023
@reasonerjt
Copy link
Contributor Author

Submitted PR for AWS plugin:
vmware-tanzu/velero-plugin-for-aws#163

I've verified that the plugin can access s3 and snapshots with this change.

I hit issue #5873 when I'm testing the B/R with Kopia, so I'll keep this issue open until I can verify this case after the work to bump kopia finishes

@reasonerjt
Copy link
Contributor Author

#6283 is merged to fix the issue on kopia path.

Closing this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area/Cloud/AWS IAM Issues related to identity and access management
Projects
None yet
Development

No branches or pull requests

1 participant