zalando / zalando/postgres-operator
AWS IRSA - Service Account Annotation
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Currently I'm using pod_service_account_definition to add annotation to the role:
configKubernetes:
pod_service_account_definition: '{"apiVersion":"v1","kind":"ServiceAccount","metadata":{"annotations":{"eks.amazonaws.com/role-arn":"arn:aws:iam::ACCID:role/postgres-role"}}}'
With this setup I'm unable to use unique role per postgres cluster - it's needed to set proper permissions on the S3 bucket.
Is it possible to generate a unique role per cluster?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with charts/postgres-operator/values.yaml and the pod_service_account_definition setting, then trace how the ServiceAccount is applied to PostgreSQL clusters. The issue does not name an implementation entry point or tests; done would require a defined, documented approach for unique AWS IRSA roles and their per-cluster permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes, postgresql
- Domain
- cloud, databases, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100