Brief introduction of K8S Source Code Analysis API Server-1 and API Server

This article mainly explains "K8S source code analysis API Server-1, API Server introduction", the content of the article is simple and clear, easy to learn and understand, now please follow the editor's ideas slowly in depth, together to study and learn "K8S source code analysis API Server-1, API Server introduction" it!

For an overall introduction to API Server, please refer to the following two articles:

Https://blog.csdn.net/huwh_/article/details/75675706

Https://blog.csdn.net/u010278923/article/details/79242791

A diagram of the overall operation of API Server:

Referring to the figure above, API Server in version 1.8 builds three server instances in turn in filter chain mode:

Api extensions server, mainly used to deal with CustomResourceDefinition

Api server, handling all resource requests in K8s, authentication and other cluster operations

Aggregator server, processing API Aggregation

Among them, Custom Resource Definition and API Aggregation are two ways to extend the functionality of K8s, allowing new functions to be added without changing the code. Api server implements all the functions of itself.

The above three server are all based on an internal structure GenericAPIServer, which can be understood as a simple http framework that can map uri to the corresponding processing logic.

Thank you for your reading, the above is the "K8S source code analysis API Server-1, API Server introduction" of the content, after the study of this article, I believe you on the K8S source code analysis API Server-1, API Server introduction to this issue has a deeper understanding, the specific use of the need for you to practice and verify. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!