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

[Housekeeping] Update aws-go-sdk to support EKS Pod Identity #5794

Closed
2 tasks done
mthemis-provenir opened this issue Oct 1, 2024 · 1 comment · Fixed by #5796
Closed
2 tasks done

[Housekeeping] Update aws-go-sdk to support EKS Pod Identity #5794

mthemis-provenir opened this issue Oct 1, 2024 · 1 comment · Fixed by #5796
Assignees
Labels
dependencies Pull requests that update a dependency file housekeeping Issues that help maintain flyte and keep it tech-debt free

Comments

@mthemis-provenir
Copy link
Contributor

Describe the issue

Currently the Go AWS SDK in use is quite old and therefore doesn't support EKS Pod Identity, which is a much simpler way to allow service accounts to associate with a role.

The minimum required versions are found here.

What if we do not do this?

Users will continue to only be able to use IRSA (IAM roles for service accounts) annotations to associate service accounts with IAM roles, which is more configuration intensive.

Related component(s)

Definitely github.com/aws/aws-sdk-go
Possibly also github.com/aws/aws-sdk-go-v2

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@mthemis-provenir mthemis-provenir added the housekeeping Issues that help maintain flyte and keep it tech-debt free label Oct 1, 2024
Copy link

welcome bot commented Oct 1, 2024

Thank you for opening your first issue here! 🛠

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file housekeeping Issues that help maintain flyte and keep it tech-debt free
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants