zalando / zalando/postgres-operator

GCS WAL backup config per cluster

Open
#2,652 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.9.0
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? GKE
  • Are you running Postgres Operator in production? yes
  • Type of issue? Question

The Postgres Operator documentation lists two ways to configure GCS access for WAL backups. However, both are global configurations at the operator level.

Is there a way to configure the WALG_GS_PREFIX (and possibly the service account or key.json) at postgres cluster level?

We previously backed up to MinIO using the Postgres S3 config. Here, I was able to set the bucket at cluster level by defining the WAL_S3_BUCKET env variable. Similarly setting WALG_GS_PREFIX in the postgres resource does not seem to work.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the administrator documentation section on Google Cloud Platform setup and inspect how the postgres resource handles WAL_S3_BUCKET. Compare that path with WALG_GS_PREFIX and the service-account or key.json settings. Done means determining whether cluster-level GCS WAL backup configuration is supported and documenting or implementing the required behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, google-cloud, kubernetes, postgresql
Domain
cloud, databases, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.