Create a plugin to add a WAL Receiver pod #74
Conversation
| RUN --mount=type=cache,target=/root/.cache/go-build ./scripts/build.sh | ||
|
|
||
| # Step 2: build the image to be actually run | ||
| FROM golang:1-alpine |
There was a problem hiding this comment.
is this what CNPG does? Or could we go distroless?
There was a problem hiding this comment.
We can do distroless, cnpg uses gcr.io/distroless/static-debian12:nonroot
| // Plugin parameter keys | ||
| const ( | ||
| ImageParam = "image" // string | ||
| ReplicationHostParam = "replicationHost" // Required: primary host |
There was a problem hiding this comment.
isn't that implicit in CNPG?
There was a problem hiding this comment.
CNPG also takes an optional image name
| ) | ||
|
|
||
| const ( | ||
| defaultImage = "ghcr.io/cloudnative-pg/postgresql:16" |
There was a problem hiding this comment.
can we have an image with just the wal reciever?
There was a problem hiding this comment.
I can try to make that, yeah
| "--port", "5432", | ||
| "--username", "postgres", | ||
| "--no-password", | ||
| "--verbose", |
There was a problem hiding this comment.
that should probbaly depend on log level
| - Automatic restart policy for high availability | ||
|
|
||
| 2. **PersistentVolumeClaim**: `<cluster-name>-wal-receiver` | ||
| - Stores received WAL files persistently |
There was a problem hiding this comment.
we need some retention policy - should integrate with backup interval or so. Ok, to make ToDo for now - but we really should delete stuff so the disk doesn't flow over
|
From the slack: |
No description provided.