Pure hand-built kubernetes (k8s) 1.9 cluster-order

Original intention

Since the advent of kubernetes (k8s), the installation of complex, difficult to deploy has been the industry to spit groove, but also a lot of beginners to block outside the door. While there are also official standalone deployment options for getting Started: Minikube, and the kubeadm used to build the cluster, the domestic green network environment makes the official program extremely complex. So the community has also sprung up with a lot of projects dedicated to deploying k8s, like Kubeasz with Ansible scripting, with more than 500 star on GitHub, and a variety of k8s-related sites with a lot of long-set articles specifically for the environment.
Whether it's an official or a community program, the following are the general reasons:

• Using ready-made binaries

  Downloading directly from an official or other third party is an executable file that k8s individual components. You can run it directly. Whether it's Centos,ubuntu or any other Linux distribution, you can run it directly if the GCC compilation environment is not very different. There is generally no cross-platform problem with newer systems.

• Compiling the installation using source code

  The compilation result is also a binary file for each component, so if you can download it directly to the required binaries, there is no need to compile it.

• Run with mirroring

  The same feature uses the services provided by the binaries, and optionally uses mirroring. Just like Nginx, like MySQL, we can use the installation version, run an executable file, or use their mirrors to run and provide the same service. K8s is the same thing, the service image provided by the binary file is also available.

From the above three ways in fact, the use of mirroring is a more elegant solution, the advantages of the container is naturally not much to say. But from a beginner's point of view, the container's scheme will be somewhat complex, not so pure, there will be a lot of container configuration files and questions about how services like binary files are provided in the container, easy to run off. So the binary way is more suitable for beginners.

Then there are classmates asked, there are a lot of binary installation of the tutorial, why do I also repeat the wheel? Indeed, K8s's binary installation method does have a lot of tutorials, I also have to look at the introduction, there are two main tutorials, one is a fool, also called a button, run a command, execute a script, all done (of course, will encounter some problems, you need to find a way to solve the ^_^). There is also a complex, step-by-step everything is written down, follow the walk again, the basic few hours passed (mainly k8s of the certification authority part is too complex), not the problem you encountered. It was out of my own way of getting started that I had this idea: to do a tutorial for beginners, so that they could build the environment, understand the architecture of k8s, understand the authentication authorization, understand the configuration of each component and the relationship between them. So I split the k8s, stripped its certification authority and service discovery, first from the core module, build good one cluster, and then practice practiced hand, and then add authentication authorization to the cluster. Make it easier for beginners to accept understanding.

Let's take a look at the following:

0, order one, pre-preparation environment two, the core module deployment three, authentication authorization and service discovery

Pure hand-built kubernetes (k8s) 1.9 cluster-order