Only if you've got a homogeneous workload that can scale out. More typical is Team A working on Project A spin up a test DB + test app server. Team B also spi

Only if you've got a homogeneous workload that can scale out. More typical is Team A working on Project A spin up a test DB + test app server. Team B also spin up a test app server + web server + DB for project B Then Project A gets productionized and you have SIT/UAT/Stage copies of all of that sitting mostly idle. Then project C comes along and the devs need to test on a 3 node C* cluster with 3 kafka brokers... Suddenly you have a whole bunch of dev environments sitting mostly idle. No-one would ever fork out on reserving a t2.medium, but they all add up to $$$$$ every month. With k8s you can reclaim all that idling power, reserve some beefy instances, whilst also gaining easily deployable artefacts, CI/CD, production scaling, etc.