[hunvreus]

I get the appeal, but personally I stay away from k8s. I don't mind putting in work to set up my deployment pipeline, but on a day to day I just want to push code to my repo and potentially edit environment variables. That's the sweet spot I was trying to hit.

[_zoltan_]

you can do that with k8s and argo?

[hunvreus]

Sure, I just wanted a simple and user-friendly experience.

[CuriouslyC]

Not trying to be dismissive here but if you're deploying regularly and you have plans to scale anything putting the time into learn and automate K8s pays off very quickly. What you're doing here gives me ORM vibes - good for training wheels and helping people that don't know stuff to be productive quickly, but ultimately a source of lots of problems that you wouldn't encounter if you didn't invest in a leaky abstraction.

[felixgallo]

Are you suggesting K8S is free of leaky abstractions?

[CuriouslyC]

I'm suggesting for this case it's closer to ground truth than a hand rolled Vercel clone, because it's been battle tested and tweaked HEAVILY.

[felixgallo]

Containers on top of K8S is radically less ground truthy than this project, and you say heavily tweaked like it’s a good thing. I doubt there is a single person alive who understands even half of all of those tweaks.