Write at the front-"read every line of code-kubernetes"

What am I going to write?

"Understand each line of code-kubernetes" will contain k8s the entire project source code analysis, considering the threshold problem, before starting to analyze the k8s I will be in some of the less difficult Golang open source projects to help you improve Golang coding skills And then through the k8s related to some of the projects, to open up obstacles to k8s learning some of the major obstacles; the final focus on fire, will kubernetes the whole source of the project thoroughly understand.

Overall, this series of plans in three steps to complete the source level to master the k8s goal:

• Golang Skill Enhancement

• K8s Dependency Technology

• K8s Core Components

At present, the k8s application of the tutorial has been many, of which there are quite good articles, so I will not specifically to explain k8s is a functional level of knowledge points. This tutorial for everyone's entry requirements is a little golang, will k8s the general operation.

Write to WHO to see

K8s's popularity does not need me to repeat, the importance of k8s technology believe that we are also clear, do not play k8s how to say that they are engaged in cloud computing?

K8s technology has a certain understanding of the technical staff, if you are interested in k8s, and hope to master this skill, and even from the source level master k8s, do a Daniel, participate in CNCF Community contribution, but suffer from the source code threshold is too high, do not know where to start, that is right, this tutorial is written to you to see!

What are the characteristics

"Read each line of code-Kubernetes" will be in the public number "Cloudgeek" and the blog Park "Cloudgeek" synchronized updates. In order to conform to the characteristics of the mobile reading time fragmentation, this tutorial each article is not too long, reading is about more than 10 minutes of the appearance, of course, to thoroughly master each line of code mentioned, may need you to open the PC, in the IDE itself to the side of the source code, this step will need to have the time and the basic skills related.

This series of tutorials from Cache2go, such as only hundreds of lines of the source of small projects began to explain, for some golang basic knowledge, but not proficient in Golang, temporarily can not directly read k8s source code but want to k8s source contributor development of it technical personnel.

In the source code analysis process will involve a number of technical topics, I will be in the "Golang Advanced-Topic lectures" and other series of special analysis. For example, the source involved in the heap operation, involving the application of various locks, consistent hashing algorithm and other aspects of the problem, I will write a special article to explain, let the friend of the technical obsessive-compulsive disorder can master k8s, instead of looking at a few lines, leaving a look do not understand the algorithm, the heart of a lump, tangled impact progress, Do not struggle to feel incomplete.

Why do you write

First of all, my main research direction in my work is the container technology stack, which is a bunch of technology in the CNCF community. In order to be able to go further in this direction, I set myself a goal: to become the member of Kubernetes organization. Becoming a member simply means being able to continuously contribute to the source code. In the process of reading the source of a lot of detours, and finally I realized that such a large project began to plunge in and easily lost in k8s huge source and third-party dependencies. So I chose to start from a small project to read the source code, the ability to upgrade, and then see k8s. I want to share this process to help more people master k8s and enjoy the fun of technology.

Another important reason is that I know that in the process of reading the source code, every knowledge point only to write, to understand others, can really explain that they understand. So write this series of tutorials is also out of the supervision of their own, output backward force input.

Write at the front-"read every line of code-kubernetes"