What is CRD primarily used for in Kubernetes?

What is CRD primarily used for in Kubernetes?

• A. Handling DNS records
• B. Storing pod logs
• C. Defining custom resource types to extend the Kubernetes API
• D. Managing nodes hardware drivers

Answer: (C)

Custom Resource Definitions extend the Kubernetes API by letting you define new resource types. This lets you model domain-specific objects with their own schema and validation, and interact with them just like built-in resources. Once a CRD is installed, you can create, read, update, and delete those custom resources, typically aided by a controller or operator that watches them and reconciles the actual state to the desired state. This is why CRDs are used to extend Kubernetes with new kinds of objects that your applications manage directly through the API. DNS handling is performed by components like CoreDNS, not by creating new API kinds; storing pod logs is managed by logging infrastructure, not by CRDs; hardware drivers for nodes are managed by node components and the kubelet, not by introducing new resource types.

Custom Resource Definitions extend the Kubernetes API by letting you define new resource types. This lets you model domain-specific objects with their own schema and validation, and interact with them just like built-in resources. Once a CRD is installed, you can create, read, update, and delete those custom resources, typically aided by a controller or operator that watches them and reconciles the actual state to the desired state. This is why CRDs are used to extend Kubernetes with new kinds of objects that your applications manage directly through the API.

DNS handling is performed by components like CoreDNS, not by creating new API kinds; storing pod logs is managed by logging infrastructure, not by CRDs; hardware drivers for nodes are managed by node components and the kubelet, not by introducing new resource types.