aws / aws/eks-pod-identity-agent
[Feature Request] Addition of an IAM controller to this project
- Dominant language
- Go
- Stars
- 96
- Forks
- 40
- Avg merge
- 23h 38m
- Merged PRs (30d)
- 7
Description
I have been managing kubernetes service account permissions with IAM for a little while, using IRSA and this new project.
I think the best solution would be to combine this project with something like the IAM controllers from: [aws-controllers-k8s](https://aws-controllers-k8s.github.io).
This would allow the creation of an IAM role via the kubernetes API, and its binding via an eks pod identity association, in a single file.
Contributor guide
Research direction
Start by reviewing this project's existing pod identity behavior and comparing it with the IAM controllers linked from aws-controllers-k8s. Define the controller scope and its Kubernetes API shape before implementation; done means an IAM role can be created and bound through an EKS pod identity association from a single file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- authorization, cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100