3 ms·
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 project
by ZalandoTech 9y ago
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 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-controller 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 https://github.com/kubernetes-incubator/external-dns)
We also have several older Postgres-related tools listed here: http://zalando.github.io/ http://zalando.github.io/.
Users and contributors very welcome; just drop a line in our projects' Issues Trackers.
- jchw 9y agoLooking forward to external-dns being merged. DNS records are probably the last thing in our Kubernetes cluster that isn't automated. I'm still not sold on using ALBs for Ingress resources. ALB is clearly superior to ELB when using them for the same things, but it seems like ALB costs will soar when using ALBs as Ingress controllers since they increased the rule limit and subsequently started charging on them. Still, the alternative of having four layers for every route seems nearly as undesirable. I really don't want ALB -> nginx -> kube-proxy -> container.
- hjacobs 9y agoThis is a bit off topic, but the mentioned Ingress controller (https://github.com/zalando-incubator/kube-ingress-aws-controller https://github.com/zalando-incubator/kube-ingress-aws-contro...) is not using the ALB rules, it just provisions ALBs with the right SSL certificate and points to some HTTP proxy doing the actual host/path routing (e.g. Skipper). See http://kubernetes-on-aws.readthedocs.io/en/latest/admin-guide/kubernetes-in-production.html#ingress http://kubernetes-on-aws.readthedocs.io/en/latest/admin-guid...
- bogomipz 9y agoI am curious did you look at Govenor(postres template for HA with etcd) before writing Patroni? https://github.com/compose/governor https://github.com/compose/governor If you did can you comment on how these might compare and why you decided to write your own? Thanks!
- hjacobs 9y agoI guess you did not look into Patroni's README, as it states: > Patroni originated as a fork of Governor, the project from Compose. It includes plenty of new features. Governor's git repo seems to have no recent activity (last commit 11 months ago).
- bogomipz 9y agoIndeed I missed that, my bad. But anyway the README states: >"Patroni originated as a fork of Governor, the project from Compose. It includes plenty of new features." But it doesn't say what those features are. So I guess I'm curious what those features are without having to watch a whole youtube video. Or why they didn't submit PRs to Govenor for the added functionality.
- CyberDem0n 9y agoCompose guys are kind of happy with existing functionality of Governor and didn't really wanted to add something new. That was the main reason of making a fork. If you read a further comments to this news you can get familiar with the part of new functionality of Patroni comparing to Governor.
- bogomipz 9y agoThanks. Yeah I've been making my way through the video - "Elephants on Automatic: HA Clustered PostgreSQL with Helm" and its discussed at the 15:57 minute mark here if anyone else is interested: https://www.youtube.com/watch?v=CftcVhFMGSY https://www.youtube.com/watch?v=CftcVhFMGSY Cheers.