Which control plane component runs the API surface?

Which control plane component runs the API surface?

• A. Scheduler
• B. Kubelet
• C. API server
• D. Etcd

Answer: (C)

The API surface of the cluster is provided by the API server (kube-apiserver). It acts as the gateway to the Kubernetes REST API for both external clients and internal control-plane components. When you interact with the cluster, requests go to the API server, which authenticates and authorizes them, validates and mutates resources through admission controllers, and stores the desired state in etcd. Other control-plane components and controllers communicate with the cluster primarily through this API server, making it the central entry point for all cluster management operations. The other options—scheduler, kubelet, and etcd—serve different roles (scheduling decisions, node-side management, and storage, respectively) and do not expose the API surface to clients.

The API surface of the cluster is provided by the API server (kube-apiserver). It acts as the gateway to the Kubernetes REST API for both external clients and internal control-plane components. When you interact with the cluster, requests go to the API server, which authenticates and authorizes them, validates and mutates resources through admission controllers, and stores the desired state in etcd. Other control-plane components and controllers communicate with the cluster primarily through this API server, making it the central entry point for all cluster management operations. The other options—scheduler, kubelet, and etcd—serve different roles (scheduling decisions, node-side management, and storage, respectively) and do not expose the API surface to clients.