What is the main purpose of the Kubernetes API?

What is the main purpose of the Kubernetes API?

• A. It stores cluster configuration locally
• B. It runs pods directly
• C. It provides operations to create, read, update and delete resources
• D. It handles only network policies

Answer: (C)

The Kubernetes API is the primary interface through which clients manage the cluster’s resources. It exposes operations to create, read, update, and delete objects like pods, deployments, services, and config maps. When you run commands (from kubectl) or when controllers and controllers’ managers perform tasks, they communicate with the API server, which authenticates and authorizes requests, validates them, and stores the desired state in a backing store (etcd). The system then uses that desired state to drive the actual state on the nodes, with controllers continuously reconciling differences. So the main purpose is to provide a consistent set of operations to manage resources across the cluster. It doesn’t run pods directly (that’s the kubelet’s job on each node), and the cluster’s configuration is stored in etcd, not locally in the API server. It manages far more than network policies, covering a wide range of resource types.

The Kubernetes API is the primary interface through which clients manage the cluster’s resources. It exposes operations to create, read, update, and delete objects like pods, deployments, services, and config maps. When you run commands (from kubectl) or when controllers and controllers’ managers perform tasks, they communicate with the API server, which authenticates and authorizes requests, validates them, and stores the desired state in a backing store (etcd). The system then uses that desired state to drive the actual state on the nodes, with controllers continuously reconciling differences.

So the main purpose is to provide a consistent set of operations to manage resources across the cluster. It doesn’t run pods directly (that’s the kubelet’s job on each node), and the cluster’s configuration is stored in etcd, not locally in the API server. It manages far more than network policies, covering a wide range of resource types.