external-dns

For special reazon, our project should use AWS ALB(not ELB) or NLB to catch an application in k8s cluster. We are using kops to manage the k8s cluster. It seems its load balancer stategy is using ELB for AWS cloud. I have researched some approach to realize it: - ELB https://github.com/kubernetes/kops/tree/master/addons/ingress-nginx - ALB https://github.com/coreos/alb-ingress-controller - External-DNS https://github.com/kubernetes-incubator/external-dns About the second ALB, it shows: NOTE: This controller is in alpha state as we attempt to move to our first 1.0 release. The current image version is 1.0-alpha.3. Please file any issues you find and note the version used. So it seems that it isn't a good choice for production environment. Then, what's the good way?

For Route53 integration, have you looked at https://github.com/kubernetes-incubator/external-dns? (or its progenitors Mate and DNS-Controller) Looks like CoreOS just contributed an ALB Ingress implementation: https://github.com/coreos/alb-ingress-controller

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.