"let the tool figure out how best to get there" doesn't really sound any different than the concept of the other systems you were describing. It sounds like th

"let the tool figure out how best to get there" doesn't really sound any different than the concept of the other systems you were describing. It sounds like the difference is largely just some implementation details: rather than a one-shot run through a DAG which will abort out if anything doesn't match the plan, I assume the kubernetes approach will just keep retrying until it converges, as if you were running "terraform apply" in a loop constantly until it tells you there are no changes left to make. Is there something about the kubernetes approach that differs in capability rather than just implementation approach? These underlying APIs are always fallible so I don't really see how you can get away from some sort of converging process where total convergence (without errors) might not actually be possible until you change the configuration.