New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

wal-g backup retention not working since 1.13.0 #2786

Open

bo0ts opened this issue Oct 21, 2024 · 0 comments

bo0ts commented Oct 21, 2024

Which image of the operator are you using? ghcr.io/zalando/postgres-operator:v1.13.0
Where do you run it - cloud or metal? Kubernetes or OpenShift? OpenShift 4.15
Are you running Postgres Operator in production? yes
Type of issue? Bug

Since upgrading to postgres-operator 1.13.0 old wal-g backups are not deleted anymore.

We use the following backup related configuration:

kind: ConfigMap
apiVersion: v1
metadata:
  name: postgres-pod-config
data:
  AWS_ACCESS_KEY_ID: ...
  AWS_SECRET_ACCESS_KEY: ...
  AWS_S3_FORCE_PATH_STYLE: "true"
  AWS_REGION: ...
  AWS_ENDPOINT: ...
  USE_WALG_BACKUP: "true"
  USE_WALG_RESTORE: "true"
  WALG_DISABLE_S3_SSE: "true"
  WAL_S3_BUCKET: ...

We suspect that this is related to the following issue in Spilo zalando/spilo#1015

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment