zalando / zalando/postgres-operator
Logical Backup not working behind proxy
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.7.0
- Where do you run it - cloud or metal? Kubernetes
- Are you running Postgres Operator in production? [yes]
- Type of issue? [ feature request ]
When running Backup job behind proxy Logical Backup container is not able to upload the update to S3
upload failed: - to s3://*************/spilo/*****-postgresql/ac6a170b-9817-4fa8-afe8-041e86e20cfe/logical_backups/1630899622.sql.gz Connect timeout on endpoint URL: "https://*************/*****-postgres-operator-backup/spilo/*****-postgresql/ac6a170b-9817-4fa8-afe8-041e86e20cfe/logical_backups/1630899622.sql.gz?uploads"
Looking at the code there is no option to set up ENV for the proxy.
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
Begin with the logical backup job/container and its S3 upload path described in the report. Check how proxy settings are passed to that job and reproduce the timeout behind a proxy. Done means the backup can upload to S3 when proxy settings are configured for the reported Kubernetes deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- cloud, databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100