Custom Resource Definitions (CRDs) in Kubernetes are a very powerful and useful bit of tech, but, as with any API, making changes safely can be a lot harder than it would seem.

At previous Kubernetes maintainer summits, we've talked about challenges for upstream CRD-based APIs, like Gateway API, Admin Network Policy and others, and what those projects are doing.

This talk is about discussing current pain points with versioning and releasing CRDs, and will include:

* a quick run through the requirements for making
safer API changes to CRDs

* some examples of versioning and release methods, and the problems that various projects have found

* Questions for future work and discussion

Come along to this talk if you're using CRDs in any capacity, in Kubernetes or other projects.