Why Kubespray?
We encountered Kubernetes just over two years ago - before that we had experience with Apache Mesos and we successfully abandoned docker swarm. Therefore, the development of k8s immediately followed the Brazilian system. No minicubes or management solutions from Google.
Kubeadm at that moment did not know how to assemble an etcd cluster, and of the other options, kubespray was in the top of Google's results.
We looked at it and understood β it is necessary to take.
September 23, 20.00 Moscow time Sergey Bondarev will hold , where he will tell you how kubespray is prepared so that it turns out tasty, efficient and fail-safe and then the thought βnot all yogurts are equally usefulβ does not arise.
At the webinar, Sergey Bondarev will tell you how kubespray works, what is the difference from kubeadm, kops, rke. He will share the unique features of kubespray and the cluster installation algorithm. Will analyze the features (disadvantages) in industrial operation.
So why are we grabbing kubespray with all three hands?
- It is ansible and opensource. You can always finish some moments for yourself.
- You can install on Centos, well, and on other distributions π
- HA setup. Failover etcd-cluster of 3 masters.
- Ability to add nodes and upgrade the cluster.
- Installation of additional software such as dashboard, metrics server, ingress controller, etc.
Also, the ansible scenario works with the mitogen. Which gives an acceleration of 10-15%, no more, because most of the time is taken by downloading images and installing.
Objectively speaking, at the moment the choice of kubespray for installing a cluster is far from being as obvious as it was two years ago.
In short...
For example, kops - like a cubespray, it allows you to install a cluster from scratch, even create virtual machines. But only AWS, GCE and open stack work. Which, as it were, raises the question - why is it needed if these clouds have solution management, even in the open stack, for example, selectel and or mail.ru. rke - someone likes it, but they have their own approach to the structure of the created cluster and not very great opportunities for customizing cluster components. Plus, an already configured node with docker installed is required. kubeadm - also requires docker, a utility from kubernetes developers, has finally learned how to create fault-tolerant setups, store the config and certificate inside the cluster, and now you donβt need to manually sync these files between nodes. A good tool, but focused only on raising the control plane. Even the network in the cluster does not install, and the documentation suggests applying the manifests with CNI manually.
Well, an important fact is that all three of these utilities are written in go, and if you need something of your own, unique, you need to know go to tweak the code and create a pull request.
Cubespray is an ansible that is clearly easier to learn than go.
Well, of course, on the same ansible, you can write your own scripts for installing docker and cluster using rke or kubeadm. And these scripts, due to their narrow specialization specifically for your requirements, will work much faster than cubespray. And it's a great working option. If you have the skills and time.
And if you're just getting started with , then mastering the cubespray will be much easier and faster.
And that's just part of what we're talking about. It will not be boring. Come and . Or register and . As you like.
Source: habr.com