The first time I came into contact with k8s in 2015, the construction process at that time was not so complicated, yum installation, manual matching, no certificate, no Dashboard, and no wall... . I haven't touched k8s for 3 years. Looking at it now, I find that the changes have changed a lot. There are all kinds of automatic deployment tools, containers, and walls... . It was rebuilt in a new way, and the reference posts were put in the front, because others wrote much better than me, so I only summarize the experience here.
1. Manually build k8s: https://www.kubernetes.org.cn/3096.html
This post is very detailed, step by step to make the certificate, modify each configuration file, and deploy it manually. However, this is not the mainstream deployment method, and it is suitable for novices to deeply understand the various components of k8s through manual construction.
2. Kubeadm builds k8s: https://www.kubernetes.org.cn/3536.html
I haven't studied the pros and cons of Kubeadm and kubespray. Maybe it's because I used ansible when I played kolla, so I feel more intimate with kubespray, but not so interested in Kubeadm. Another interesting thing is that most of the posts on Kubeadm deployment are 16 years old, while most of the kubespray posts are 17 years old. The start of kubespray on github is also much higher than that of Kubeadm, so now the mainstream is kubespray?
Closer to home, the level of detail in the post is average. Although it was written in 18 years, the content is a bit old. The trouble with building is to engage in rpm packages such as kubeadm and mirrors such as pause-amd64. I got related stuff through google virtual machine, but it is still very troublesome in general. After all, it's not mainstream, so I didn't study it carefully.
3. Kubespray builds k8s:
https://www.jianshu.com/p/68925cb902e7
https://www.cnblogs.com/iiiiher/p/8128184.html
Kubespray's deployment posts are more comprehensive, and the mirrors are all placed in the Alibaba Cloud warehouse by the author, and it is also very convenient to download the mirrors. The difference from the post is that the version of docker-ce I installed is a bit high, docker-ce-17.12.1.ce-1.el7.centos, and the kubespray provided by the author needs to verify docker-engine-selinux (in It's gone in docker-ce-17.12.1 version). So I changed the kubespray/roles/docker/vars/redhat.yml configuration file and removed the docker_selinux check. Other reference posts, change the IP or something. In general, the construction process is very smooth. It takes about 3 hours from the new virtual machine installation system to the completion of deployment.
Last picture, mark it
