What Is a Kubernetes CRD?

Kubernetes CRD is a Custom Resource Definition, a mechanism that lets you extend the Kubernetes API by defining entirely new resource types. Once a CRD is registered, users can create, read, update, and delete instances of the custom resource using kubectl and the Kubernetes API, just like native resources such as Pods and Services. CRDs are the foundation of the Kubernetes operator pattern.

Why CRDs Matter

The built-in Kubernetes resources cover general-purpose workloads, but organizations often need to manage domain-specific resources like databases, certificates, or monitoring configurations. CRDs allow you to model these domain concepts as first-class Kubernetes objects, leveraging the existing Kubernetes API, RBAC, and tooling. This extensibility is what makes Kubernetes a platform for building platforms.

CRDs have become the standard way to extend Kubernetes functionality. Tools like cert-manager, Prometheus Operator, and Argo CD all use CRDs to define their resources. Understanding CRDs is essential for working with the broader Kubernetes ecosystem, as nearly every production add-on introduces custom resources that operators need to understand and manage.

How CRDs Work

You define a CRD by creating a YAML manifest that specifies the new resource's name, API group, version, and schema. When you apply this manifest, Kubernetes registers the new resource type and creates API endpoints for it. Users can then create instances of the custom resource using standard kubectl commands. A custom controller watches for changes to these resources and takes action, forming the operator pattern that powers advanced automation.

Understanding how kubernetes crd fits into the broader cloud-native ecosystem is important for making informed architecture decisions. It works alongside other tools and practices in the DevOps and platform engineering space, and choosing the right combination depends on your team's specific requirements, scale, and operational maturity.

Key Features

API Extension

CRDs add new resource types to the Kubernetes API without modifying or recompiling the API server itself.

Schema Validation

Define OpenAPI schemas for custom resources to validate their structure and reject invalid configurations.

Native Tooling

Custom resources work with kubectl, RBAC, namespaces, and all standard Kubernetes tooling out of the box.

Versioning

CRDs support multiple API versions with conversion webhooks, enabling safe schema evolution over time.

Common Use Cases

Defining a PostgresCluster custom resource that an operator uses to provision and manage database clusters automatically.

Creating Certificate resources that cert-manager uses to issue and renew TLS certificates from Lets Encrypt.

Building custom workflow resources that represent CI/CD pipelines as native Kubernetes objects.

Modeling infrastructure components like VPCs and DNS records as Kubernetes custom resources managed by Crossplane.

How Obsium Helps

Obsium's Kubernetes consulting team helps organizations implement and optimize kubernetes crd as part of production-grade infrastructure. Whether you are adopting kubernetes crd for the first time or looking to improve an existing implementation, our engineers bring hands-on experience across cloud platforms and Kubernetes environments. Learn more about our Kubernetes consulting services →