What does CRD stand for in the context of Container Orchestration?

What does CRD stand for in the context of Container Orchestration?

• A. Custom Resource Definitions
• B. Container Resource Directives
• C. Central Registry Definition
• D. Cluster Resource Descriptors

Answer: (A)

CRD stands for Custom Resource Definitions. In Kubernetes, the API can be extended by defining new resource types through CustomResourceDefinition objects. When you apply a CRD, you register a new kind of resource, specify its fields and validation, and choose its scope. Once the CRD is in place, you can create and manage resources of that new type just like built-in Kubernetes resources, enabling operators to declaratively manage complex applications and external systems. The other terms listed aren’t standard Kubernetes terminology, so they don’t represent how the API is extended.

CRD stands for Custom Resource Definitions. In Kubernetes, the API can be extended by defining new resource types through CustomResourceDefinition objects. When you apply a CRD, you register a new kind of resource, specify its fields and validation, and choose its scope. Once the CRD is in place, you can create and manage resources of that new type just like built-in Kubernetes resources, enabling operators to declaratively manage complex applications and external systems. The other terms listed aren’t standard Kubernetes terminology, so they don’t represent how the API is extended.