Earlier quoted context omitted.
Gosh, there is job title for capacity planning?
do capacity planners buy and sell capacity to scale up and down month to month? :)
When does the need ever go down?
Kubernetes a black hole of unpredictable spend, according to new report
21–30 of 88 posts
Re: Kubernetes a black hole of unpredictable spend, according to new report
#22Earlier quoted context omitted.
do capacity planners buy and sell capacity to scale up and down month to month? :)
When does the need ever go down?
If you're retail, it goes down after xmas. If you're a tax company, it goes down after may. If you sell a product, it goes down when you go long enough without releasing anything new
Re: Kubernetes a black hole of unpredictable spend, according to new report
#23A lot of the “finops” practitioners I’ve seen are myopically focused on tagging of AWS resources; and that falls to pieces with kubernetes because AWS can’t see inside the kubernetes clusters.
I’m not surprised they don’t like it.
Re: Kubernetes a black hole of unpredictable spend, according to new report
#24Re: Kubernetes a black hole of unpredictable spend, according to new report
#25A lot of the “finops” practitioners I’ve seen are myopically focused on tagging of AWS resources; and that falls to pieces with kubernetes because AWS can’t see inside the kubernetes clusters. I’m not surprised they don’t like it.
Yup. Particularly because k8s scales based on whole system load, not single app load. It's harder to predict because it's better at optimizing resource utilization and ultimately lowering costs.
Re: Kubernetes a black hole of unpredictable spend, according to new report
#26I mean, what did anyone think the cloud was? This isn't news.
Re: Kubernetes a black hole of unpredictable spend, according to new report
#27A lot of the “finops” practitioners I’ve seen are myopically focused on tagging of AWS resources; and that falls to pieces with kubernetes because AWS can’t see inside the kubernetes clusters. I’m not surprised they don’t like it.
Yup. Particularly because k8s scales based on whole system load, not single app load. It's harder to predict because it's better at optimizing resource utilization and ultimately lowering costs.
You can scale load on many things in more recent versions of K8s. for example, pubsub depth of un-acked messages, or custom metrics in prometheus format.
https://cloud.google.com/kubernetes-engine/docs/tutorials/au...
Re: Kubernetes a black hole of unpredictable spend, according to new report
#28I think the articles headline is a little rude to Kubernetes. I’m by no means a fan of Kubernetes, especially not in non-tech enterprise, but the article is really about the unpredictable and rising cost of moving into the cloud that is owned by the big tech companies, isn’t it? Sure kubernetes can be part of that, but you can easily run into the same predicament without it. The unpredictability of cost is actually t…
When we pushed a bunch of teams at a large retailer from ec2 to kubernetes in ec2 (not eks) we reduced overall cloud spend by ~30%.
It's only unpredictable and unquantifiable if you don't look at it. Is the problem that they don't have the right tools to look at it yet?
Re: Kubernetes a black hole of unpredictable spend, according to new report
#29Earlier quoted context omitted.
do capacity planners buy and sell capacity to scale up and down month to month? :)
When does the need ever go down?
At night, often. For example, I have had a use case where we needed a 1000 node build farm during the day when developers were working, but only 50 at night. Machine learning jobs are another common source of workloads that need burst capacity.
Re: Kubernetes a black hole of unpredictable spend, according to new report
#30A lot of the “finops” practitioners I’ve seen are myopically focused on tagging of AWS resources; and that falls to pieces with kubernetes because AWS can’t see inside the kubernetes clusters. I’m not surprised they don’t like it.
I just had a meeting with a 'finops' manager where i showed him how kubernetes has a similar tagging structure (labels) and how we can break down per team pricing based on cpu/memory utilization.
It's not hard, you just need the tools (kubecost, etc)