Can/should Weave GitOps manage the CRD lifecycle? If not, how do it's users do that?

[scottrigby]

Can we use Weave GitOps to manage CRD lifecycle? @scottrigby do we have any documentation on how to do this using Flux Kustomize Controller?

To be clear, this is something Flux can currently do by using a Kustomization file to order first any CRD updates, and then any Helm chart updates that would depend on those. This example repo doesn't show it, but does show how with pure Flux Kustomize and Helm can work together: https://github.com/fluxcd/flux2-kustomize-helm-example

If I understand correctly, Weave GitOps hides most of this from users in an attempt to simplify the experience. Is the idea that users should manage their CRD updates with their own hand-made kustomization files like Flux does? Or is there an interest in essentially doing this same thing for users based on some wego/UI configuration?

See #39 #50