[anoncoward1234]

Kubernetes is cool and all, but there needs to be a lot of simplification for it to be "nice to use". Essentially the problem is that it's the "opposite" of Golang - the number of ways to do the same thing is massive leading to huge numbers of headaches in trying to get things done.

Recently, I spun up a simple pod-to-pod communication example but I found it pretty difficult. If you look up cluster networking in Kubernetes (https://kubernetes.io/docs/concepts/cluster-administration/n...) you'll find a whole fire hose of different options from ingress to calico to fabric and on and on.

This was what it took for me to try and rubber ducky my way to getting networking to work on Kubernetes, and in the end I had to get help from a friend at work (https://stackoverflow.com/questions/50195896/how-do-i-get-on...). It may be better than what came before, but it's not great.

[shaklee3]

Kops, kubeadm, rancher, kubespray all do what you want, but differently depending on your needs. What were you looking for?

[anoncoward1234]

EXACTLY

[shaklee3]

I don't see your point, but I should have clarified more:

Kops == AWS install Rancher == Easy small cluster on-prem or private cloud. GUI push-button setup kubeadm == CLI tool to set up a cluster manually with basic settings. Not very flexible, but can get a cluster working in minutes. kubespray == Ansible playbooks for setting up k8s cluster. The most powerful of the bunch, especially if you're familiar with ansible. This is the preferred way to run it in production I believe, along with customizations on top.

[outworlder]

Why don't you use something like Kops? It will create (and manage) the cluster for you.