What feature allows you to extend the Kubernetes API by defining new resource types?

What feature allows you to extend the Kubernetes API by defining new resource types?

• A. Operators
• B. Admission Controllers
• C. Custom Resource Definitions
• D. API Aggregation

Answer: (C)

Custom Resource Definitions enable extending the Kubernetes API by registering a new resource kind, along with its group, version, and schema. Once a CRD is applied, the API server recognizes the new type, so you can create, read, update, and delete objects of that kind just like built-in resources. This sets up a platform for building controllers or Operators that watch those custom resources and take automated actions to achieve the desired state. While Operators are a common pattern that manage these resources, the mechanism that introduces the new resource type is the CRD. Admission Controllers handle validation or mutation of requests and do not define new resource kinds, and API Aggregation involves adding external API servers to extend the API surface rather than registering new resource types within the core Kubernetes API.

Custom Resource Definitions enable extending the Kubernetes API by registering a new resource kind, along with its group, version, and schema. Once a CRD is applied, the API server recognizes the new type, so you can create, read, update, and delete objects of that kind just like built-in resources. This sets up a platform for building controllers or Operators that watch those custom resources and take automated actions to achieve the desired state. While Operators are a common pattern that manage these resources, the mechanism that introduces the new resource type is the CRD. Admission Controllers handle validation or mutation of requests and do not define new resource kinds, and API Aggregation involves adding external API servers to extend the API surface rather than registering new resource types within the core Kubernetes API.