Looks interesting. I currently deploy dev instances as a single pod with everything in it, basically exactly the same as what devs get if they run docker compose locally. It works but pretty wasteful for many cases that don't need their own db etc. Is this supposed to make that less wasteful? Is it any different in the "full app"/end to end mode?
Yes, Kardinal is designed to make development environments more efficient and less wasteful compared to your current setup, where each dev instance is a single pod with everything in it. In Kardinal, we calculate reusability at the application level. You only deploy the services you're actively working on, which means you won't need to spin up unnecessary components, like a separate database, if it's not needed for your dev/test case. This will improve both cost and speed.