A lightweight tool to facilitate config reuse, designed for GitOps, config as data, and composition with other tools and formats.https://twitter.com/GoogleOSS/status/1245026820979859464 …
Show this thread
-
kustomize and kpt seem to promote any changes to be explicitly written into files, resulting in unwanted dirty state in some workflows (local iterations with HEAD builds, or generated secrets). Are these not supported as anti-patterns, or too rare to be part of happy path?
kustomize and kpt support treating different customization cases distinctly and composing them together, rather than treating them all the same (e.g. inline parameter substitution). But they are declarative, so something new may be needed if you want to configure them on the fly