postgres-operator
postgres-operator copied to clipboard
zalando
Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
Anyone else using ArgoCD to deploy this operator? I'd like to suggest we create an ArgoCD "Custom Health Check" for this operator. Read more about what that is here: https://argo-cd.readthedocs.io/en/stable/operator-manual/health/...
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.6.0 - **Where do you...
Addresses https://github.com/zalando/postgres-operator/issues/2065 - [ ] open issue for this - [ ] check spilo-role: standby_leader for the standby (open issue/adjust doc)
Please, answer some short questions which should help us to understand your problem / question better? Possible to set it in spilo via https://github.com/zalando/spilo/pull/755 - **Which image of the operator...
…PI down (#2031) I think the refactor in https://github.com/zalando/postgres-operator/pull/1848 has introduced this regression, do you think it was intended? Before the refactor, `getPodEnvironmentSecretVariables` and `getPodEnvironmentConfigMapVariables` were called directly in `generateStatefulSet`...
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.8.2 - **Where do you...
- **Which image of the operator are you using?** e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.8.2 registry.opensource.zalan.do/acid/postgres-operator:v1.8.2 - **Where do you run it - cloud or metal? Kubernetes or OpenShift?** [AWS K8s | GCP ......
> We've removed the `required` flag for `resources` in the CRD schema starting from `v1.8.0`. _Originally posted by @FxKu in https://github.com/zalando/postgres-operator/issues/2028#issuecomment-1234071399_ This isn't enough to not have any CPU/memory limits...
in the OperatorConfiguration CRD "pod_environment_secret" and "pod_environment_configmap" properties is located under "kubernetes" object. aws_or_gcp object does not have these properties.
I already opened a ticket on Wall-E side: https://github.com/wal-e/wal-e/issues/425 I am curious if there are other things we would need to do on the operator side. The integration is just...
