zalando / zalando/postgres-operator
Configure a standby and primary for S3 WAL streaming
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? ghcr.io/zalando/postgres-operator:v1.11.0
Where do you run it – cloud or metal? Kubernetes
Type of issue: Question
Hello, I have a few questions regarding the PostgreSQL Operator setup:
-
Could you provide an example or template demonstrating how to deploy a primary cluster with S3-based WAL archiving enabled, along with a standby cluster that uses it?
-
Does the standby cluster require a full cloning before it can start using WAL streaming? What is the correct procedure to initialize a standby cluster from scratch if it's using S3 bucket?
-
Is it possible to configure multiple standby clusters—one replicating via S3 WAL and another using direct TCP streaming replication?
-
In case of a standby promotion, is there a way to roll back the promotion, or is it an irreversible operation?
Appreciate your assistance with this!
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
The issue names no files, tests, or code entry points; start by reviewing the PostgreSQL Operator's existing documentation and configuration guidance for S3 WAL archiving, standby initialization, replication modes, and promotion. Done means providing verified examples and clear answers to each of the four questions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100