This was the point of "devops" (the concept, not the job title): the team should be responsible for development and operations, so one isn't prioritised hugely over the other.
replyBut those things all require more pods on the cluster! We've looped back around to the beginning.
replyExactly my point.
But then developers: "I just want to go to my Heroku days again!" but then with a sufficient big company there are maaany developers doing things their slightly different way, and then other effects start compounding, and then costs go up because 15 different teams are using 27 different solutions and and and...
replyBut yeah, let's just spin-up a shadow IT VM with Debian like GP said, it's easy!
> But yeah, let's just spin-up a shadow IT VM with Debian like GP said, it's easy!
replyThat’s literally how they sold AWS in the beginning.
Cloud won not because of costs or flexibility but because it allowed teams to provision their own machines from their budget instead of going through all the red tape with their IT departments creating… a bunch of shadow IT VMs!
Everything old is new again, except it works on an accelerated ten year cycle in the IT industry.