A report on Kubernetes expenditure from the Cloud Native Computing Foundation (CNCF), in association with the FinOps Foundation, shows that costs are rising and companies struggle to predict them accurately.
The new report is based on a survey of the CNCF and FinOps Foundation communities and although it had only 195 respondents, there was a "strong enterprise representation".
Spending on Kubernetes was up, according to the survey, with 67 per cent reporting an increase of 20 per cent or more over the last 12 months, and 10 per cent spending more than $1m per month on their deployments.
Kubernetes, as Reg readers know, is a means of orchestrating containerised applications, so its actual cost is mainly that of the resources it consumes: over 80 per cent compute (such as VMs on AWS, GCP or Azure) and a bit on memory, storage, networking and so on.
The cost of such things as training IT staff and maintaining complex deployments was sadly not a focus of the report. Rather, its key point was that many organisations have only a loose grip on what they are spending.
"The vast majority of respondents… either do not monitor Kubernetes spending at all (24 per cent), or they rely on monthly estimates (44 per cent)," the report said.
Of those which do use tools, the favourites specified were largely the cloud provider's tools such as AWS Cost Explorer, Azure Cost Management, and GCP Cost Management, though there was a significant showing for the open source KubeCost with 12 per cent adoption. The humble spreadsheet came in at 5 per cent.
Accurate prediction of Kubernetes costs is a challenge
Less than 25 per cent of those surveyed said they could accurately predict how much they’d spend on Kubernetes to within 5 per cent of actual cost. However, the figure climbed to circa 60 per cent when they were asked if they could predict spend to within 10 per cent of the real cost.
Over 20 per cent apparently stated "we do not predict our cloud bill" though that was not correlated to size of organisation so may represent mainly small deployments.
There is evidence though that the exact size of the monthly Kubernetes bill comes as a bit of a surprise to many companies, which is far from ideal given the high and increasing cost of the technology.
- What the heck is FinOps? It's controlling cloud spend – and new report says it ain't easy
- Enterprise databases deployed in Kubernetes? Proceed with caution, warns seasoned analyst
- What Microsoft's Windows 11 will probably look like
- VC's paper claims cost of cloud is twice as much as running on-premises. Let's have a look at that
According to FinOps Foundation, the solution is to do a better job of tracking expenditure. Suggestions include combining real-time Kubernetes cluster costs with additional costs such as database instances and cloud storage use, drilling down to the nodes, pods and persistent volumes and carefully tagging and allocating each resource, and to automate cost reports to track trends.
Controlling and reducing Kubernetes costs is not inherently different from managing other kinds of IT costs, but the abstraction it offers perhaps makes it easier to miss the detail of the resources consumed. There is also the challenge of scaling appropriately to the demand, with over-provisioning all too easy.
"Worship at the altar of 'turn that shit off'. You're charged for what you forget to turn off," cloud cost consultant Corey Quinn told us last year. The fact that it is Kubernetes should be no exception. ®