Logical Backup not working behind proxy

[hz47]

• 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.

[stephan2012]

Just hit the same issue. K8s with the Postgres Operator runs locally and shall backup to an AWS S3 backup but Internet connection is possible via proxy only. While it is possible to add http_proxy, https_proxy, and no_proxy to pod_environment_configmap, these variables become available for the root user only.

[stephan2012]

This is actually a Spilo issue, I think. So we should raise it there.

[CyberDem0n]

@stephan2012 Spilo never deals with logical backups.