zalando / zalando/postgres-operator
Backup job images service account auth to access s3 buckets due to outdated awscli
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- helm chart 1.10.1, backup image registry.opensource.zalan.do/acid/logical-backup:v1.10.1
- aws eks
- used in production
- bug report
We are using role-based auth and pod identity agent to provide access to resources required and switching to logical backup for some resources.
While running logical backup cronjob, it fails with
Unsupported host '169.254.170.23'. Can only retrieve metadata from these hosts: 169.254.170.2, localhost, 127.0.0.1
generally issue can be solved by installing awscli from binary.
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 locating the logical-backup image build or chart configuration for registry.opensource.zalan.do/acid/logical-backup:v1.10.1 and inspect how its AWS CLI obtains credentials. Reproduce the backup cronjob on AWS EKS with the Pod Identity Agent; done when role-based access to the S3 bucket works without the unsupported metadata-host error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes, postgresql
- Domain
- cloud, databases, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100