'%3e%3crect%20width='64'%20height='64'%20fill='url(%23fk)'/%3e%3crect%20width='64'%20height='64'%20fill='url(%23bk)'/%3e%3c!--%20Concentric%20radar%20rings%20--%3e%3cpath%20d='M64.0%2014.0A14%2014%200%200%201%2050.0%200.0'%20fill='none'%20stroke='%23fff'%20stroke-opacity='.25'%20stroke-width='1.3'/%3e%3cpath%20d='M64.0%2024.0A24%2024%200%200%201%2040.0%200.0'%20fill='none'%20stroke='%23fff'%20stroke-opacity='.25'%20stroke-width='1.3'/%3e%3cpath%20d='M64.0%2034.0A34%2034%200%200%201%2030.0%200.0'%20fill='none'%20stroke='%23fff'%20stroke-opacity='.25'%20stroke-width='1.3'/%3e%3cpath%20d='M64.0%2044.0A44%2044%200%200%201%2020.0%200.0'%20fill='none'%20stroke='%23fff'%20stroke-opacity='.25'%20stroke-width='1.3'/%3e%3cpath%20d='M64.0%2054.0A54%2054%200%200%201%2010.0%200.0'%20fill='none'%20stroke='%23fff'%20stroke-opacity='.25'%20stroke-width='1.3'/%3e%3c!--%20Thicker,%20high-visibility%20signal%20lime%20arc%20(stroke-width%205.2%20for%20small%20navbar%20display)%20--%3e%3cpath%20d='M54.8%2033.2A34%2034%200%200%201%2030.2%206.5'%20fill='none'%20stroke='%23C8F55B'%20stroke-width='5.2'%20stroke-linecap='round'/%3e%3c/g%3e%3c/svg%3e)
The basics
- Label every workload with team, service and environment, and enforce it at admission.
- Attribute cost by the resources each pod requests, and compare it to what it actually uses.
- Share the cost of common services, such as the control plane and ingress, by an agreed rule.
The pitfalls
- Unlabelled workloads pile up in an “unallocated” bucket.
- Requests set far above real use waste capacity for everyone.
- Idle capacity has to belong to someone.
Use the numbers
- Show each team its own cost.
- Flag the largest gaps between requested and used resources.
- Set requests from measured use.
- Review after each change.
Sources and further reading
- Kubernetes documentation. Resource management for pods and containers. kubernetes.io/docs.
IICTP is a new independent credential and is not ISO/IEC 17024 accredited.