Session
Don’t Do What Charlie Don’t Does - Avoiding Common CRD Design errors
Most controllers written for Kubernetes include their own Custom Resource Definition (CRD) - but it’s actually very easy to make mistakes in the CRD design that will cost a lot in longer-term maintenance.
Come and hear from Gateway API and Ingress controller maintainers about Charlie Don’t, the Kubernetes developer with the worst luck in designing CRDs, and how you can use his experience to avoid the most common problems with CRD design.
You should expect to come away from this session with an understanding of common CRD design errors and the ways you can avoid them.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top