Kubernetes API big picture
Kubernetes is API-centric — all resources are defined in the API, and all communication goes through the API server.
Administrators and clients send requests to create, read, update, and delete objects like Pods and Services. For the most part, you’ll use kubectl to send these requests. However, you can craft them in code or generate them through API testing and development tools. The point is, no matter how you generate requests, they always go to the API server where they’re authenticated and authorized. They’ll be executed on the cluster if they pass the auth tests. If it’s a create request, the object is deployed to the cluster and persisted to the cluster store in its serialized state.
Figure 15.1 shows the high-level process and highlights the central nature of the API and API server.
Let’s start busting some jargon.
JSON serialization
What does it mean to persist an object...
