So much saturation in this space of people trying to create one off solutions, which on some level I admire. However the further off the main path you go the more you lock yourself into problems you can't troubleshoot or edge cases that aren't supported.
Abstraction these days is alluring, and it's cool! However you want something well known, well supported, (from multiple companies ideally) and documented. The hate for understanding kubernetes is just hate for having to understand layers of orchestration, or worse the layers behind the application.
If it's too complicated then you might not need it. Any platform you use will have those same layers, it just depends on how much is assumed or exposed to you. If you don't want to see any dials or options then use a managed solution, not a roll your own platform tool. That's of course assuming a few virtual machines managed by hand doesn't satisfy your needs, but if that's the case you don't need a platform solution (and hopefully it's not production).
I still think that projects like this one come from necessity. Folks want to have an alternative for vendor lock-in.
I'm building something like that too (https://github.com/pier-oliviert/sequencer) for Kubernetes, and it's also out of necessity.
Vercel, Heroku and others have a lot of helpful tools that are empower developers, and I think people want to have those without being locked-in.
It goes without saying that I'm totally bias :)
because a well-configured k8s cluster nullifies the need for this project. also hi!
It's really hard to fault k8s these days, all the original problems are solved and all that remains is necessary complexity that can't be abstracted without lowering power.
That doesn't mean you can't abstract over it, you can and should but you should do so in the scope of your team or organisation where you already know which pieces of power you need/want or otherwise know the way you which you want to leak those capabilities.
It's not like netlify does better in terms of rightizing nodes.