Everything has to go in Kubernetes these days… usually at the request of users who lack the relatively trivial skill to convert a Compose definition into a set of Kubernetes resources.
Or Product Managers/C-Suites/Directors who believe Kubernetes is the future of computing and if it's not in there it's garbage that should be thrown out.
Source: Senior IT Engineer who likes K8s as a concept, but is incredibly disappointed with its unnecessary complexity and everyone's insistence on its use without understanding its role or purpose.
Yeah, was thinking that as well. IMHO, compose.yaml is the best balance of convenience and simplicity if you need one (or even "several") instances. You should only get more fancy if you need to deploy `n` instances with auto provision/load-balancing/failover/etc.
Hey, thank you for the feedback. I have created an issue to add a quick start for Kubernetes as well. Most of my decisions behind this project is to make it super "dumb" and easy to use. Thank you so much for the feedback!