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

datamgr-for-vsphere-plugin support for IRSA #544

Open
mafitconsulting opened this issue Jul 20, 2023 · 0 comments
Open

datamgr-for-vsphere-plugin support for IRSA #544

mafitconsulting opened this issue Jul 20, 2023 · 0 comments

Comments

@mafitconsulting
Copy link

Describe the problem/challenge you have

In our on-premise setup with vanilla Kubernetes, we have implemented IAM Roles for Service Accounts (IRSA) to establish connectivity between our on-premise environment and AWS. While Velero and the Velero plugin for AWS support IRSA, it seems that the datamgr-for-vsphere-plugin does not currently provide IRSA support. Instead, the plugin expects the cloud-credential file to be consistently available and mounted.

Describe the solution you'd like

Enhance functionality of the datamgr-for-vsphere-plugin to include support for IRSA, similar to the implementation demonstrated in the AWS plugin. You can refer to the specific code section in the AWS plugin repository that showcases this functionality:

velero-plugin-for-aws/object_store.go#L290-L302

By incorporating IRSA support into the datamgr-for-vsphere-plugin, our aim is to enable seamless integration and utilise the security benefits provided by IRSA for our on-premise Kubernetes environment.

Anything else you would like to add:
In the absence of a code change that directly incorporates IRSA support, we can explore potential workarounds to use IRSA until the feature is officially added.

Environment:
velero 1.11
velero-plugin-for aws v1.7.0
velero-plugin-for-vsphere v1.5.1
kube v1.26.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant