The Kubernetes ecosystem is rife with tools like this, and it feels like such a chore to just keep up with every new templating system for YAML files. I have started to just write Go programs that directly talk to the Kubernetes API and manage my rollouts (one step away from operators).
It's more curly brackets than YAML :)
Instead, kpt's key design philosophy is to keep configuration as data. This makes it easier to develop tooling that operate on configs.
If you are going to introduce a new tool into an already crowded ecosystem the least you can do is describe why anyone should use it.
Kpt is an OSS tool for Kubernetes packaging. It uses a standard format to bundle, publish, customize, update, and apply configuration manifests. Kpt operates like kubectl, providing additional functionality to prune and delete configuration.
I've banned this account, but if you want to use it to participate in the community as a regular member, you're welcome to email firstname.lastname@example.org and let us know.