CRD stands for what in Kubernetes?

CRD stands for what in Kubernetes?

• A. Custom Resource Definitions
• B. Core Resource Descriptor
• C. Custom Resource Descriptors
• D. Cluster Resource Definitions

Answer: (A)

CRD stands for Custom Resource Definitions. It’s the mechanism Kubernetes provides to extend the API with new resource kinds. By creating a CRD, you declare a new type (with its group, version, and kind), specify how it should be named and whether it’s namespaced or cluster-scoped, and define its validation schema. Once the CRD is applied, you can create instances of that new resource type, and typically a custom controller or operator watches and reconciles those resources to implement whatever behavior you need. The other options aren’t standard Kubernetes terms for API extension, so they aren’t correct.

CRD stands for Custom Resource Definitions. It’s the mechanism Kubernetes provides to extend the API with new resource kinds. By creating a CRD, you declare a new type (with its group, version, and kind), specify how it should be named and whether it’s namespaced or cluster-scoped, and define its validation schema. Once the CRD is applied, you can create instances of that new resource type, and typically a custom controller or operator watches and reconciles those resources to implement whatever behavior you need. The other options aren’t standard Kubernetes terms for API extension, so they aren’t correct.