zalando / zalando/postgres-operator
Add the podServiceAccount.create option
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
https://eksctl.io/usage/iamserviceaccounts
I created a service account with eksctl, but it was overwritten by initPodServiceAccount, so I had trouble.
To avoid this, I have eksctl create the ServiceAccount again after running initPodServiceAccount, but it's annoying to have to worry about it every time.
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 by tracing the initPodServiceAccount path and the podServiceAccount configuration, then review the eksctl IAM service account behavior described in the linked documentation. Done means podServiceAccount.create controls whether the operator creates or overwrites the ServiceAccount, with tests covering the option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100