m²
m²
Having the exact same issue on ubuntu 20.04 using helm v3.8.1 Any clues what's going wrong?
@mprimeaux building the operator on an aarch64 (linux/arm64) machine (Google Cloud Tau T2A GCE Instance) worked out for me, i.e. customizing the Makefile+Dockerfile and overriding the operator's default image (helm...
@arezvani maybe you have some connectivity issues on your side? Pulling the image works w/o any problems:  For me, this issue seems not related to the postgres-operator itself.
@arezvani nope, not at all. Just try the command you can see in the screenshot yourself. The docker file can be found under docker/Dockerfile and docker builds can be done...
@arezvani Nope. I don't think that this will help you. If you need the docker image, go build it your self, eg. run `make docker` Cheer's and pls close this...
@iampranabroy did you found an interim solution? Facing the same issue and I think (for now) the only way to go is to deploy an separated zookeeper cluster. Will dig...
~However, can confirm that the described solutions, i.e. increasing the livenessProbe.initialDelaySeconds, works. Setting this to 30s I was able to successfully deploy a zookeeper cluster with replicas > 1.~ //Edit:...
@HoustonPutman yes, solved it without using any probes. The problem was related to wrong NetworkPolicies and old (maybe corrupted) configs in the zookeeper PVC, cf. https://github.com/pravega/zookeeper-operator/issues/315#issuecomment-1259187314
@iampranabroy yes, all resources (Solr + ZK) in the same namespace with NetworkPolicies denying all pod's egress traffic.
@mprimeaux spilo linux/arm64 support has been merged yesterday https://github.com/zalando/spilo/pull/790 and will be available with the next spilo tag (postgresql version >= 14 support only). Now we can continue with the...