Arun Kumar
Arun Kumar
@eleanor-millman any update on feature request?
I agree with @AnisTigrini . Also consider adding support for major key/value stores like `consul` etc
@FxKu any comments or feedback?
@FxKu: Thanks for your comments, after upgrade to `1.8.1` there are no such failures.
We are also facing similar issues. When I dig into the pods, found that `/home/postgres/pgdata/pgroot/data/pg_wal` directory has lot for wal log files. The wal log files were not cleaned, hence...
@pockyhe : Even after upgrading to `v3.4.1`, I see this error but the deployment gets completed with error `expected < 2 pods, got 2 - this is a bug` ....
@FxKu we are really looking `--insecure` or `--tls-no-verify` kind of flags for logical backup pods, since there are no way to add CA cert to the pod. Please consider as...
but the operator keeps on recreating the pods due to difference in the pod spec(additional volume in postgres )
@FxKu : Can you guys fix this as a priority?
I think the issue is not resolved. The problem here is that the S3 SSL cert is a self-signed cert. Hence the backup job pods don't have S3' CA cert....