Many complaints are about the choice of YAML as a config file format. It is being used for nearly everything, and in many cases fine details of its syntax matter, especially around multiline strings and text blocks[0]. In theory, one can always retreat to JSON, but that's barely better.

Then it goes on: you need additional tools like Helm or Kustomize to generate your YAML files. I am not aware whether anybody has ever tried to generate Kubernetes config files from Dhall[1] input files.

[0]: https://yaml.org/spec/1.2.2/#23-scalars

[1]: https://dhall-lang.org/

Probably has to do with becoming mired in duplicated abstractions. I don't think this is the same thing, though, kubernetes composes what it is intended to replace with a different set of goals.

you start with the notion that Kubernetes is too complicated. so you build your own deploy and hosting system, add features to it as they come up, and soon you've reinvented Kubernetes poorly