linkerd / linkerd/website

CRDs in Kubernetes: The Good, The Bad And The Ugly

Open
#128 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/blog priority/P1 size/medium type/tutorial
Dominant language
JavaScript
Stars
60
Forks
221
Avg merge
4h 32m
Merged PRs (30d)
1

Description

### What is the purpose of the post?

The purpose of this post is to educate architects and SREs about how CRDs are used and how they can impact applications and architectures under the hood in meaningful ways.

### What should it talk about?

The post will explain what are CRDs (custom resource definitions) in Kubernetes, what they do, and their benefits and weaknesses (specifically that CRDs are not "free lunches" - that using them in the wrong way or using too many of them can have significant consequeneces for application performance"

### Who is the target audience?

* [x] Architect
* [x] SRE
* [] Developers

### Are there any assets?
Ideally, this should have some assets or a brief screen shot series showing how to check for the number of CRDs or how to view CRDs being deployed

### What are the dependencies?
None

### Relevant Examples / References

https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
https://blog.heptio.com/an-introduction-to-extending-kubernetes-with-customresourcedefinitions-76deb675b27a

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the two linked Kubernetes and Heptio references, then inspect the website's existing post structure and contribution guidance. Draft an article for architects and SREs covering CRDs, their benefits and weaknesses, and performance implications, with the requested screenshots; done means the post and assets are ready for review.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.