[x0rg]

Great stuff, happy to see this, especially the part that concerns the setup of the cluster, but still too much in early stages. Currently I'm learning a lot on how to get started on AWS and it is still a bit too painful... after using GKE you just don't want to deal with the manual setup.

[Axsuul]

Also don't forget about minikube, which allows you to play around with a kubernetes cluster locally. You should really be working with this before even attempting to setup a cluster in the cloud.

[010a]

You should check out kops. It seems to me like its one level of abstraction above kubeadm, and makes creating clusters on AWS _ridiculously_ easy (one command).

[DigitalJack]

I'd like to try out kops, it sounded good. But step one was setting up a zone on route53, we don't use route53. Kube-aws from the coreos folks makes the same assumption, but is still useable, however it doesn't have multi-az capability.

I love kubernetes and I can't wait for the tooling to mature. I'm about to give 1.4 a spin and see where things stand.

[yissachar]

You can use Route53 for just a subdomain even if your parent domain is not done through Route53, see https://github.com/kubernetes/kops/blob/master/docs/creating...

[x0rg]

Plus, kube-aws doeesn't really allow of easy maintenance of the cluster (i.e. cluster updates) as far as I know.

[x0rg]

I'll definitely do it, too bad for the 50 nodes limitation that can't fit my use case.

[yissachar]

That's only if you use VPC networking. If you use external networking, you can deploy a networking Daemonset (Weave, Flannel, etc.) and there's no 50 node limit.