-
#### Describe the task
From Platform Services: The current version of the Crunchy operator is the last version with Postgres 14 compatibility. The operator will need to be upgraded in preparation for…
-
Hi
`(~.) = binaryOperator "~."`
should be
`(~.) = binaryOperator "~"`
-
- Which image of the operator are you using?
public.ecr.aws/c7a1d1p6/tsdb:postgres-operator-v1.10.0-v2
- Where do you run it - cloud or metal? Kubernetes or OpenShift?
This is running on EKS …
-
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.13.0
- …
-
I am not sure where the right repo for this issue would be, so I am filing it here, as we encountered the problem while trying to get the operator to work.
**Describe the bug**
Postgres version 15…
-
### Search before asking
- [X] I searched the [issues](https://github.com/sqlfluff/sqlfluff/issues) and found no similar issues.
### What Happened
PostgreSQL, MySQL, and SQLite all support the JSO…
-
Hello!
Apologies for posting an issue ticket; Discussions seem to be disabled on this repo.
I had recently been struggling a lot with the Zalando Postgres Operator - having moved the cluster onc…
-
##### SUMMARY
When using the `kubernetes.core.helm` module with the `release_values` parameter it is possible to encounter an issue stemming from filtering that occurs in the `yaml.dump` oper…
-
### AC
As a developer,
I want to use the Postgres Operator database on the cluster,
So I can use its latest features
### ToDo
- Devise a migration process from the current spilo/patroni insta…
-
Thanks a lot for your work, it has benefited us a lot.
We do have one problem tho, which might be caused by some operator bug, but I thought I would ask here;
After having added `log-exporter` sid…