Disable Etcd about spilo HOT 4 CLOSED

Hi @CyberDem0n,

sorry for my late answer, I was quite busy last period. I will make a PR with the fix.
I am using Spilo both with Kubernetes and with 3 different instances of docker-compose (running on 3 different hosts). I need Postgres as a backend for Kong gateway with replication and self election. Furthermore I use HAProxy to point the Postgres' master, using a check on Patroni's port.

Kong instances will point to HAProxy.

The PR is the #197

from spilo.

Thanks @hjacobs, the project looks great. I will test it on my k8s cluster.

from spilo.

Hi @joe-pll,

configure_spilo.py tries to detect you environment (aws, gce, openstack, kubernetes). In case if it is something different, it assumes that you just start it in a docker container on your local machine and creates etcd.conf: https://github.com/zalando/spilo/blob/master/postgres-appliance/configure_spilo.py#L517 for supervisor.

You are actually right, if there is either ETCD_HOST or ETCD_DISCOVERY_DOMAIN environment variables set, configure_spilo.py should not create etcd.conf
Can you please create a PR fixing it?

And one more question, can you explain a little bit more about your setup? I am just curios, where and how do you run Spilo?

from spilo.

@joe-pll as you mention Kubernetes: please also check out our Postgres Operator for Kubernetes (it uses Patroni under the hood), we are currently migrating first production databases to it 🎉 👉 https://github.com/zalando-incubator/postgres-operator

from spilo.