However, now that I have a cluster up and running, I can take the time to build a parallel cluster with more understanding, and migrate the services to it.
I found a terraform example, but it declares itself out of date, and looked more complicated than I thought it should be... that was just a gut feel though.
I have not used Salt, but I always like to learn new things, especially if they make my life easier.
I'd be very interested in checkout out your setup, and any lessons learned you have to share.
Thanks in advance
I just need to generalize it a little bit. Email me and I will send you a link once it's done, sometime next week (I'm on vacation).
I've been playing with https://github.com/kz8s/tack lately, but your implemention sounds like even more comprehensive.
Terraform + Ansible for K8S on CoreOS
Official upcoming replacement for kube-up
I don't know what the future of Kubernetes setup is, exactly, but right now it's quite safe to settle on Salt, Puppet, Ansible or Terraform. I haven't used Terraform, so I don't know how suitable it is to OS-level setup (things that the aforementioned tools are good at), as opposed to orchestration.
Basically what's arguably the best publicly available Kubernetes setup in the world is hiding in that Salt codebase, and EVERY would-be Kubernetes admin should look at it before venturing on their own.
There's no getting away from configuration management and software installation at SOME level of your stack, and setting up a substrate for Kubernetes is no exception.
Just look how google runs stuff! https://cloud.google.com/compute/docs/tutorials/setup-joomla
Kubeup is designed to run once, unlike systems such as Puppet and Terraform that declaratively set up the world to fit your specification.
Kubeup also does a lot of mysterious stuff. By using it, you don't have a clear idea of which pieces have been set up and how they slot into each other. It is, in short, opaque and magical.
For comparison, I set up Kubernetes with Salt on AWS. It was, by all means, "the hard way", and took me a few days to get running and a couple of weeks to run completely correctly (a lot of stuff, like kubeconfig and TLS behaviour, is still undocumented), but as a byproduct I now have the entire setup in a reproducible, self-documenting, version-controlled config.