Support Flux Kustomizations CRD
See original GitHub issueHello! Thanks for putting out monokle
I tried using this with FluxCD, and found a quirk worth reporting. There is generally good support for arbitrary custom resources, however the Flux CRDs include a resource called Kustomization
in the kustomize.toolkit.fluxcd.io/v1beta2
API group.
This differs from the Kustomization
in SIG-CLI although it is closely related, it is a separate resource kind.
Unfortunately it looks like monokle treats all resources with the kind
Kustomization as SIG-CLI Kustomizations, even when they are not in a file kustomization.yaml
or one of the other magic filenames picked up by SIG-CLI Kustomize as a Kustomization.
In my example repo, https://github.com/kingdonb/bootstrap-repo I have a cluster root at clusters/moo-cluster
which contains a bunch of Flux Kustomizations, most of which point to a target directory that contains a SIG-CLI Kustomization.
The SIG-CLI Kustomize Overlay looks good in monokle:
![Screen Shot 2022-01-22 at 10 45 34 AM](https://user-images.githubusercontent.com/3286998/150645515-cc6f5894-bf0e-46ec-9d18-39ad437bc80f.png)
The Flux Kustomization is detected improperly and shows up as invalid, as it’s not validated against the OpenAPI spec from the cluster CRD, but instead against the SIG-CLI Kustomize validation schema, I guess? It doesn’t show up as a resource at all in Monokle. I haven’t read the source code to explain it yet, but I hope this is an easy fix!
![Screen Shot 2022-01-22 at 10 47 09 AM](https://user-images.githubusercontent.com/3286998/150645566-9d823cf1-ff0b-482f-b727-6ec040947453.png)
Thanks again for releasing Monokle!
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (10 by maintainers)
This has been the best drive-by issue report in the history of reporting issues 👍 awesome. I’ll look for it in the next nightly, (or in the final release if it gets there first!)
I also discovered #1199 while playing around with this - fixed in #1201 !