I don't know if it's the best way, but the way I've been managing kubernetes at work is with a custom typescript library to interface with kubernetes. That libr

I don't know if it's the best way, but the way I've been managing kubernetes at work is with a custom typescript library to interface with kubernetes. That library has two frontends, a website and a CLI. Whenever I add some new feature to the cloud I prototype it in YAML first and then when I get it working I integrate it into the program. It works mostly pretty well. It's a lot more organized and powerful than having a bunch of YAML. It does feel a bit "heavy" though. There's also parts of the kubernetes api that are hard to deal with (log streaming for instance..) I don't put everything in the tool though. Anything that's a one-off I just check in YAML for. But anything that you might do repeatedly I add to the CLI, and the website is for more general non-ops use