Kubernetes api server

As explained in Google Anthos in Action

kube-apiserver is the Kubernetes control-plane component that exposes and processes the Kubernetes API.

The Kubernetes API server is the front door to a cluster. Requests from users and services enter through it, including kubectl commands, Kubernetes Dashboard operations, and direct JSON API calls. It encapsulates etcd and acts as an event-driven hub: other components communicate through the API server, while controllers watch for relevant change events. section 3.2.2

A request commonly crosses these responsibilities:

• Accept a request to create a Pod and coordinate with the Kubernetes scheduler. section 3.2.2
• Expose cluster state through clients such as kubectl, the Kubernetes Dashboard, and direct JSON API calls. section 3.2.2
• Provide the communication path used by worker-node components; after scheduling, the kubelet retrieves Pod specifications from the API server. section 3.2.3
• Support operational diagnosis by making component interactions and request paths central to tracing cluster problems and root causes. section 3.2

Creating a Pod

A client submits a Pod-creation request to the API server. The API server communicates with the scheduler, which selects a worker node. The kubelet on that node then retrieves the Pod specification from the API server and creates the Pod. section 3.2.2 section 3.2.3

Figure 3.5 Cluster component communications

Use the cluster component communication diagram to trace how the API server connects control-plane and worker-node responsibilities. section 3.2.3

How Google Anthos in Action covers it

How deep it goes

Explains request flow, etcd encapsulation, event watching, scheduling, and kubelet retrieval without detailing API-server internals.

Examples

Uses Pod creation, scheduler placement, kubelet retrieval, and GKE on-prem kubeconfig targets as concrete request-path examples.

What it assumes

Assumes a basic understanding of Kubernetes control-plane and worker-node components.

What you can do after

Diagnose cluster interaction and workload-deployment problems by tracing requests through the API server and connected components.

How it connects

Connects kubectl, Kubernetes Dashboard, JSON API, etcd, scheduler, controllers, kubelet, and worker nodes.

liveBookmanning.com

Read Google Anthos in Action on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Acing the Certified Kubernetes Administrator Exam, Second EditionThe Kubernetes API server is the control-plane component that exposes the Kubernetes API and serves as the entry point for cluster communication.
• 

  liveBookmanning.com
  Kubernetes in Action, Second EditionThe Kubernetes API Server is the control-plane component that validates API requests, persists Kubernetes objects, and notifies interested components of changes.
• 

  liveBookmanning.com
  Cyber Threat HuntingThe Kubernetes API server is the control-plane component that exposes the Kubernetes API and processes requests to manage cluster resources.

Compare how 4 books explain kubernetes api server →

Related concepts

• etcduses · etcd is an open-source distributed key-value store providing strongly consistent storage for configuration, service discovery, and cluster or application state.
• kubectlused by · kubectl is the Kubernetes command-line client for communicating with the Kubernetes API and managing cluster resources.
• control plane nodepart of · A control plane node is a Kubernetes cluster machine that hosts components managing cluster state, exposing the cluster API, scheduling workloads, and coordinating operations.
• kubeletused by · The kubelet is the Kubernetes node agent that manages Pod containers, ensures they run according to their specifications, and reports their status to the control plane.
• control planepart of · A control plane is the management and coordination part of a system that governs the configuration, policies, state, and operations of its components and resources.
• admission controllerused by · A Kubernetes admission controller intercepts API requests after authentication and authorization, validating or mutating them before they are persisted.

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.