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

Allow to configure worker's IRSA through worker's ServiceAccount annotation #645

Closed
rparme opened this issue Jun 4, 2024 · 0 comments · Fixed by #694
Closed

Allow to configure worker's IRSA through worker's ServiceAccount annotation #645

rparme opened this issue Jun 4, 2024 · 0 comments · Fixed by #694
Labels
enhancement New feature or request

Comments

@rparme
Copy link

rparme commented Jun 4, 2024

When it comes to connecting to an S3 bucket, the documentation and the blog suggest to either use aws_access_key_id / aws_secret_access_key or to grant permission to the Kubernetes node IAM role.

I believe this misses a more granular permission mechanism and I suggest to add to possibility to define the annotations of the ServiceAccount the workers run with so that an IRSA can be linked, as already done for the controller's ServiceAccount.

An even more granular possibility would be to configure the used IRSA in the backend configuration: either configure storage.aws_secret_access_key + storage.aws_access_key_id or (new) storage.iam_role_for_service_account (this means we know the namespace and the name of the ServiceAccount as it is required to create the IRSA).

@mwylde mwylde added the enhancement New feature or request label Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants