Commodore provides opinionated tenant-aware management of Kapitan inventories and templates. Commodore uses Kapitan for the heavy lifting of rendering templates and resolving a hierachical configuration structure.
There's already a draft PR to add kustomize to the Commodore container image: #430
Additionally, we'll want at least basic documentation showing how to call kustomize from a component. We may be able to use Kapitan's external input type to run kustomize. This will require the standalone kustomize binary to be present in the path when Commodore is running.
Alternatives
Continue downloading kustomize manifests and patching them in Jsonnet
Context
We've written a bunch of components where we manually download upstream manifests which are intended to be rendered with kustomize, e.g. https://github.com/projectsyn/component-kyverno/. By having to download and render all manifests individually instead of being able to leverage kustomize, errors can happen, e.g. https://github.com/projectsyn/component-kyverno/pull/46
There's already a draft PR to add
kustomize
to the Commodore container image: #430Additionally, we'll want at least basic documentation showing how to call kustomize from a component. We may be able to use Kapitan's external input type to run kustomize. This will require the standalone
kustomize
binary to be present in the path when Commodore is running.Alternatives