aws-load-balancer-controller

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?

Or something akin to this: https://github.com/coreos/alb-ingress-controller And the blog post with a full writeup: https://aws.amazon.com/blogs/apn/coreos-and-ticketmaster-col... Or for the ELB stuff and not the ALBs: https://github.com/sky-uk/feed

Tectonic is Enterprise Kubernetes. We start with pure upstream Kubernetes at the core and install it in a production ready setup with the Tectonic Installer[1] across clouds or bare metal. On top of those basics Tectonic provides things most organizations need: - Authentication backed by LDAP/SAML/etc - One-click automated updates of the entire cluster - Pre-configured cluster monitoring/alerting There is a bunch more in there and in the roadmap too but that gives you a taste. The other thing is that we provide professional services, training, and support to customers on the whole stack from the VM or machine on up to the Kubernetes API. We have done neat collaborations with customers like the ALB Ingress Controller[2] too. [1] https://github.com/coreos/tectonic-installer [2] https://github.com/coreos/alb-ingress-controller

Yes, it's not specifically a criticism of kops. Supporting ALB as an ingress controller seems to be the direction, with the coreos contributed code the likely winner.[1] Thought it worth mentioning though, as the older ELB+k8s isn't great, and because the ALB support hasn't shaken out yet, a cluster created with kops could be suboptimal unless you address it afterwards. I assume once it all shakes out, kops would support whatever the direction is. [1] https://github.com/coreos/alb-ingress-controller

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