The Kubernetes API is often described as a CRUD interface. What does CRUD stand for in this context?

The Kubernetes API is often described as a CRUD interface. What does CRUD stand for in this context?

• A. Create, Read, Update, Delete
• B. Create, Run, Update, Destroy
• C. Copy, Read, Update, Delete
• D. Create, Read, Upload, Delete

Answer: (A)

In Kubernetes, CRUD describes the four basic operations you perform on resources: creating new objects, reading or inspecting existing ones, updating their configuration, and deleting them. This is why the API is described as a CRUD interface. Creating an object corresponds to sending a manifest to the API server (often via kubectl apply or create); reading is done with get or list to see the current state; updating involves changing fields in the object (via kubectl apply, patch, or replace); and deleting removes the resource (kubectl delete). The usual HTTP verbs map to these actions: POST for create, GET for read, PUT or PATCH for update, and DELETE for delete. Other terms like Run, Destroy, Copy, or Upload don’t align with how Kubernetes handles resource operations.

In Kubernetes, CRUD describes the four basic operations you perform on resources: creating new objects, reading or inspecting existing ones, updating their configuration, and deleting them. This is why the API is described as a CRUD interface. Creating an object corresponds to sending a manifest to the API server (often via kubectl apply or create); reading is done with get or list to see the current state; updating involves changing fields in the object (via kubectl apply, patch, or replace); and deleting removes the resource (kubectl delete). The usual HTTP verbs map to these actions: POST for create, GET for read, PUT or PATCH for update, and DELETE for delete. Other terms like Run, Destroy, Copy, or Upload don’t align with how Kubernetes handles resource operations.