Generate KUDO Manifests

[kensipe]

We already generate CRDs and have a target for that. For dev only, it makes sense to generate needed manifests. This target and script, generates all the kube objects manifests, separates them by file and renames them to logical names.

When we have agreement on this.... we can add another target to quickly setup a cluster for dev. It would likely be something like:

k apply -f config/manifests/
k apply -f config/crds/

Then we can update #1581 to use this manifest file for updates.

The startup of a dev env should be something like:

kind create cluster

# if needed
make generate-manifests

# in separate term 
ngrok http 443

#  deploys crds and manifest and updated tunnel
make dev-ready

make run

Signed-off-by: Ken Sipe kensipe@gmail.com

[zen-dog]

This target makes a lot of sense to me but why do we need to commit the manifests as part of the repo? We should have only one source of truth and that's kudo init for now.

[kensipe]

this is exactly consistent with our CRD generation

[zen-dog]

if anything, I'd like to get rid of the config/crds folder altogether. we only need for tests but once we have a beforeAll step in kuttl, we could remove the in favor of kudo init call. I'd rather not add new manifests there

[ANeumann82]

I mostly agree - things that can be generated shouldn't be checked in usually.

I'm ok with having them checked in, especially the CRDs, as the controller-gen step takes quite a while. Would be nicer to not have them checked in though.

[zen-dog]

The generate-manifests target is great, however, I don't think we should have manifests as part of the repo.

[zen-dog]

🚢