YAML hell. It's very difficult to have standard, company (or org) wide "templates" for creating resources. And I don't mean literal templates. In my ideal wor

YAML hell. It's very difficult to have standard, company (or org) wide "templates" for creating resources. And I don't mean literal templates. In my ideal world, everything would be defined within Starlark. And we could build our own abstractions. Do we want every resource to be associated with a team or cost-center label? Cool - this is now a required argument for the make_service() function. Even with Kustomize, there's a lot of context switching needed to understand fully what resources a simple service is comprised of. And depending on the team, you don't need to know all of them. But because they are files crafted by hand — or at best, initially generated by a common template and modified by hand later — it's extra stuff to pay attention to.