(Looked here and in slack but didn't find relevant entries)

The helm ordering logic (https://github.com/kubernetes/helm/blob/v2.6.1/pkg/tiller/kind_sorter.go#L29-L53) does not explicitly account for CRDs and/or custom controllers.

Are there plans to fold these in explicitly to helm?

Are they already implied by the APIService entry in the ordering?

In practice, it seems there are at least some cases in which a custom resource ought to be defined early so other resources could refer to it. I have not had a chance to try this myself but a colleague has said that helm does not handle this case well.

Are we missing something?

Are there plans to enhance helm's handling of this case?

Thanks.