Custom Resource Definitions (CRDs): Extending Kubernetes ๐Ÿš€

Custom Resource Definitions (CRDs): Extending Kubernetes ๐Ÿš€


3 min read


Kubernetes has established itself as the de facto standard for container orchestration, making it easier than ever to manage and scale applications. Yet, every environment is unique, and one size does not always fit all. Enter Custom Resource Definitions (CRDs), a powerful feature that allows you to extend Kubernetes functionality by defining custom resources and controllers. In this blog post, we'll delve into CRDs, why they are needed, the problems they solve, and provide a real-time example with a step-by-step approach to create them. Let's get started! ๐ŸŒŸ

Why Do We Need CRDs? ๐Ÿค”

Kubernetes provides a rich set of resources like Pods, Services, and ConfigMaps, but what if your application needs to manage something that Kubernetes doesn't natively support? This is where CRDs come to the rescue. They empower you to define your own custom resources, enabling you to model and manage domain-specific objects within Kubernetes.

The Problems CRDs Solve ๐Ÿ› ๏ธ

1. Abstraction and Automation

Imagine you're running a microservices-based application, and you want to automate the provisioning of database instances for each microservice. Kubernetes itself doesn't have a built-in resource for databases, so you'd typically manage this manually or with external tools. CRDs allow you to create a "Database" custom resource, abstracting away the complexity and enabling automation through Kubernetes.

2. Consistency and Standardization

CRDs ensure consistency by providing a standardized way to define, configure, and manage your custom resources. This consistency is vital when you have multiple teams or clusters, as it reduces operational friction and potential errors.

3. Kubernetes-Native Experience

With CRDs, you can leverage Kubernetes' native tooling and commands to manage your custom resources. kubectl can be used to interact with custom resources just like built-in ones, offering a seamless experience for operators and developers.

A Real-Life Example: Creating a "Website" CRD ๐ŸŒ

Let's walk through creating a simple "Website" CRD to demonstrate how CRDs work in practice.

Step 1: Define the CRD YAML

Create a YAML file, website-crd.yaml, with the following content:

kind: CustomResourceDefinition
    - name: v1
      served: true
      storage: true
  scope: Namespaced
    plural: websites
    singular: website
    kind: Website
      - web

In this YAML:

  • group specifies the API group for our CRD.

  • versions defines the API versions we support.

  • scope specifies whether the custom resource is namespaced or cluster-wide.

  • names defines the naming conventions for our custom resource.

Step 2: Apply the CRD

Use kubectl to apply the CRD definition:

kubectl apply -f website-crd.yaml

Step 3: Create a Custom Resource

Now, let's create a custom resource of type "Website." Create a file named my-website.yaml with the following content:

kind: Website
  name: my-website
    serviceName: backend-service
    port: 80

Apply the custom resource:

kubectl apply -f my-website.yaml

Step 4: Verify and Interact

You can now use kubectl to interact with your custom resource, just like any other Kubernetes resource:

kubectl get websites
kubectl describe website my-website

Conclusion ๐ŸŽ‰

Custom Resource Definitions are a powerful tool in the Kubernetes toolbox. They enable you to model and manage domain-specific resources, extending Kubernetes to fit your unique needs. By abstracting away complexity, ensuring consistency, and providing a Kubernetes-native experience, CRDs empower you to take control of your Kubernetes environment and automate tasks that were once manual. So go ahead, define your custom resources, and unlock the full potential of Kubernetes! ๐Ÿ’ช๐Ÿ†

Happy Kubernetizing! ๐Ÿšข๐ŸŒŸ

๐Ÿ” Checkout GitHub Repository for projects:


๐Ÿ” Check out my YouTube channel - Prasad Suman Mohan:


Did you find this article valuable?

Support Prasad Suman Mohan by becoming a sponsor. Any amount is appreciated!