I agree with this for internal tools only intended to be used by a relatively small organization. Using a DSL may well be preferable for open source, and for la

I agree with this for internal tools only intended to be used by a relatively small organization. Using a DSL may well be preferable for open source, and for larger organizations where not every team is proficient in your Turing-complete language of choice. Some drawbacks of plain YAML, and of tools that use string templating to render YAML: - difficult to extend features not exposed by upstream - composition is often messy, resulting in duplication - validation is often impractical (at least identifying the exact source of the error… I’m looking at you Helm!) Unrelated to OP, but you can leverage Tanka to extend helm charts with functionality not provided by upstream. https://tanka.dev/ https://tanka.dev/