postgres-operator

postgres-operator copied to clipboard

DB Passwords managed outside (Vault), how to trigger rollout restart ?

3

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.11.0 - **Where do you...

vhurtevent

Reading the values.yaml from the Helm chart: ``` configGeneral: # the deployment should create/update the CRDs enable_crd_registration: true ``` makes me think, that a Helm upgrade would upgrade the CRDs....

fgleixner

Possibility of running multiple replicas for postgres-operator pods

1

Please, answer some short questions which should help us to understand your problem / question better? - **Which image of the operator are you using?** - v1.10.0 - **Where do...

gris-gris

Please, answer some short questions which should help us to understand your problem / question better? - **Which image of the operator are you using?** ghcr.io/zalando/postgres-operator:v1.12.2 - **Where do you...

olivier-derom

- **Operator Version?** - ghcr.io/zalando/postgres-operator:v1.8.2 - **Where do you run it - cloud or metal?** Bare-metal K8s - **Type of issue?** Bug Report Hi, I saw that one of the...

shubham-yewalekar

Allow chained references of custom environment variables to all generated envs

1

Fixes #2227 Currently custom environment variables are added after _most_ generated envs but notably before `WAL_BUCKET_SCOPE_SUFFIX` and `_PREFIX`. This means that referencing one of these values from a custom env...

siegenthalerroger

Would it be possible to add https://github.com/IvorySQL/IvorySQL support to the operator? Or is that already somehow possible to use it as a replacement?

mgerhardy

Please, answer some short questions which should help us to understand your problem / question better? - **Which image of the operator are you using?** e.g. ghcr.io/zalando/postgres-operator:v1.13.0 ghcr.io/zalando/postgres-operator:v1.14.0 - **Where...

notwaf

feat(logical-support): add sse_c support to aws s3 cp

2

`aws s3 cp` needs `--sse-c` and `--sse-c-key` args work with SSE-C. `LOGICAL_BACKUP_S3_SSE_C` and `LOGICAL_BACKUP_S3_SSE_C_KEY` was added to the backup script. These new variables can be passed to logical_backup using `logical_backup_cronjob_environment_secret`.

aslafy-z

Please, answer some short questions which should help us to understand your problem / question better? - **Which image of the operator are you using?** e.g. ghcr.io/zalando/postgres-operator:v1.13.0 ghcr.io/zalando/postgres-operator:v1.12.2 - **Where...

notwaf