CRDs and Helm
Consider this email an invitation to get involved.
Wouldn’t it be good if Helm was better with CRDs? Helm currently has the `crd-install` lifecycle hook. In charts we can use the Capabilities to detect if a CRD is already present (with improvements in that coming). But, people want more. How do we get there?
CRDs are hard for several reasons:
This is just to illustrate the complexity. There is more to it.
There have been some ideas and discussion on the topic including:
Both of these have issues that need to be designed around.
Do you have ideas on making this work or solving some of the design problems? If so, we welcome the insight and help.