I suspect a big chunk of this is simply visibility: if you deploy an application using your cloud provider’s native features, you get an itemized bill telling y

I suspect a big chunk of this is simply visibility: if you deploy an application using your cloud provider’s native features, you get an itemized bill telling you where your money is going. That’s not perfect (you still need to tag resources) but it’s mature and familiar. If you run everything in Kubernetes - which, to head off a popular tangent, is not just following a fad but a trade off - you have to build and operate the equivalent infrastructure to have the same level of visibility, but since the entire Kubernetes cluster is overhead it’s very easy to get stuck in the IT shared services pitfall where there’s a constant pressure to direct limited resources towards application-visible work. The survey’s reported breakdown feels right – you need solid leadership to resist the urge to skimp on indirect infrastructure costs and I’d bet most of the 80% know this is a problem but have been too busy to spend time on it: > just under a fifth (19%) had access to accurate information, while 40% said they estimated their Kubernetes costs. There was no monitoring in place for 38%.