Kubernetes
"Traditional FinOps cost allocation (e.g. mapping costs of resources back to teams or projects) doesn’t work. You can’t simply allocate the cost of a resource, such as EC2 instance to a tag or label..."
A developer experience platform has been adopted by over 10,000 users, while a Kubernetes platform supports several hundred projects.
Overprovisioning CPU and memory will keep the lights on, but it is costly. Underprovisioning them risks CPU throttling and out-of-memory kills, which cause applications to perform poorly or even crash."
Google says "we've taken several steps to reduce the risk of users making authorization errors with the Kubernetes built-in users and groups, including..."
Hammer down those AWS bills, chisel away at that scheduling latency; pick a carpentry tool, pick your clumsy metaphor...
"Once an attacker is past the initial access, the opportunities are ample for lateral movement and privilege escalation within a cluster..."