spilo

Zalando open source evangelist here. Some of my colleagues are on this thread, taking your questions. Meanwhile, wanted to plug a few other Postgres/K8s projects we're working on: -- Spilo: HA PostgreSQL cluster using Docker (https://github.com/zalando/spilo) -- kube-ingress-aws-controller: Configures AWS Load Balancers according to Kubernetes Ingress resources (https://github.com/zalando-incubator/kube-ingress-aws-contro...) -- external-dns: a Kubernetes Incubator collaboration. Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services. (https://github.com/kubernetes-incubator/external-dns) We also have several older Postgres-related tools listed here: http://zalando.github.io/. Users and contributors very welcome; just drop a line in our projects' Issues Trackers.

> Stolon is quite comparable to Patroni and has more features than Patron. Let me as a question, what feature Stolon has and Patroni doesn't? Can you give an example? From my side I can provide list of features available in Patroni, but not in Stolon. For example: * there is no way to do a controlled failover (switchover) in Stolon. * in Patroni it's possible to exclude some nodes from a leader race. * Patroni supports cascading replication * Patroni can take basebackup from replicas if they are marked with a special tag * it's even possible to configure Patroni to use a custom backup/recovery solution instead of pg_basebackup * Patroni can give you a hint that postgres must be restarted to apply some configuration changes * with Patroni it's even possible to schedule switchover or restart restart of postges on some specific time (for exa

Yes, we are currently developing a PostgreSQL operator for Kubernetes. We are heavy PostgreSQL users. Spilo[0] supports all kinds of slave configurations, backups, monitoring tools[1] and all advanced capabilities. [0] https://github.com/zalando/spilo [1] https://github.com/zalando/PGObserver Edit: https://github.com/zalando/patroni is a better link