Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kubernetes a black hole of unpredictable spend, according to new report

theregister.com

Post reply on HN
Print view View original

11–20 of 88 posts

Re: Kubernetes a black hole of unpredictable spend, according to new report

#11

Post by KurtMueller »

ferdowsi wrote: post #4
gnivol wrote: post #3

This is not counting the people costs involved, kube experts ain't cheap. Complexity is only going up. Suggestion for next article -> "Software a black hole of unpredictable spend"

From the application engineer side I'm not convinced that Kubernetes is particularly complex. I recently ramped up on it and found it liberating, frankly. Once I understood the basic concepts it was much more sensible than staring at a mountain of bespoke Ansible scripts operating on components I could barely see or understand. I can't speak to the SRE side; I can imagine the complexity there. But are these challenge…

I have a basic Ruby on Rails app up on Kube but with no authentication and no SSL certificate. What should I learn next to add these things? How did you learn these things?

Re: Kubernetes a black hole of unpredictable spend, according to new report

#12

Post by scns »

KurtMueller wrote: post #11
ferdowsi wrote: post #4

Earlier quoted context omitted.

From the application engineer side I'm not convinced that Kubernetes is particularly complex. I recently ramped up on it and found it liberating, frankly. Once I understood the basic concepts it was much more sensible than staring at a mountain of bespoke Ansible scripts operating on components I could barely see or understand. I can't speak to the SRE side; I can imagine the complexity there. But are these challenge…

I have a basic Ruby on Rails app up on Kube but with no authentication and no SSL certificate. What should I learn next to add these things? How did you learn these things?

Use Traefik as your Ingress, done.

Re: Kubernetes a black hole of unpredictable spend, according to new report

#14

Post by scns »

scns wrote: post #12
KurtMueller wrote: post #11

Earlier quoted context omitted.

I have a basic Ruby on Rails app up on Kube but with no authentication and no SSL certificate. What should I learn next to add these things? How did you learn these things?

Use Traefik as your Ingress, done.

Correcton: for TLS, Auth still has tbd.

Cant edit since on mobile

Re: Kubernetes a black hole of unpredictable spend, according to new report

#15

Post by joana035 »

reedciccio wrote: post #6
moksly wrote: post #2

I 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…

Renting the hardware is not necessarily a cost-saving measure though: how much of the compute/storage capacity you have is sitting idle in your datacenter? That's the whole point of finops: you need to have full visibility into the usage of your infrastructure so you can optimize the spend.

Gosh, there is job title for capacity planning?

Re: Kubernetes a black hole of unpredictable spend, according to new report

#16

Post by fimbulvetr »

KurtMueller wrote: post #11
ferdowsi wrote: post #4

Earlier quoted context omitted.

From the application engineer side I'm not convinced that Kubernetes is particularly complex. I recently ramped up on it and found it liberating, frankly. Once I understood the basic concepts it was much more sensible than staring at a mountain of bespoke Ansible scripts operating on components I could barely see or understand. I can't speak to the SRE side; I can imagine the complexity there. But are these challenge…

I have a basic Ruby on Rails app up on Kube but with no authentication and no SSL certificate. What should I learn next to add these things? How did you learn these things?

Maybe using cert-manager & ingress-nginx to front the service with SSL. Then your ingress-nginx will front your ruby app and decorate it with ssl. Please note, and I am embarrassed it took me so long to figure out - there are two nginx ingress projects - "nginx-ingress" and "ingress-nginx"! I would strongly recommend using the k8s official one, which is ingress-nginx. See: https://www.digitalocean.com/community/tutorials/how-to-set-...

This will help you learn the ingress pattern. After that, I would suggest exploring ways to tack a sidecar on (log aggregator, etc) - my impression is you are just looking for things to learn, I wouldn't normally suggest doing this just to do it.

Alternatively, you could try exploring putting grafana/prometheus in, though this can be a big bite for someone learning, so I would recommend learning/comprehending sidecars/ingress, etc as they are some of the building blocks for k8s.

Edit: I see there's another comment for traefik for ingress - that's fine too, it's the concept that matters, not your particular choice. If you have a lot of trouble implementing one, try the other one, things you learn in your journey will help quite a bit.

Re: Kubernetes a black hole of unpredictable spend, according to new report

#17

Post by reedciccio »

joana035 wrote: post #15
reedciccio wrote: post #6

Earlier quoted context omitted.

Renting the hardware is not necessarily a cost-saving measure though: how much of the compute/storage capacity you have is sitting idle in your datacenter? That's the whole point of finops: you need to have full visibility into the usage of your infrastructure so you can optimize the spend.

Gosh, there is job title for capacity planning?

do capacity planners buy and sell capacity to scale up and down month to month? :)

Re: Kubernetes a black hole of unpredictable spend, according to new report

#18

Post by Decker87 »

tyingq wrote: post #8

"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." The premise seems off to me. Of course people have a hard time predicting the cost of an autoscaling infrastructure that they haven't had for a long time. Presumably they moved off of a fixed size infrastructure to get to Kubernetes. Where they were either paying for ex…

Geez, We can barely predict anything within 5%.

Re: Kubernetes a black hole of unpredictable spend, according to new report

#20

Post by gizdan »

ferdowsi wrote: post #4
gnivol wrote: post #3

This is not counting the people costs involved, kube experts ain't cheap. Complexity is only going up. Suggestion for next article -> "Software a black hole of unpredictable spend"

From the application engineer side I'm not convinced that Kubernetes is particularly complex. I recently ramped up on it and found it liberating, frankly. Once I understood the basic concepts it was much more sensible than staring at a mountain of bespoke Ansible scripts operating on components I could barely see or understand. I can't speak to the SRE side; I can imagine the complexity there. But are these challenge…

I have been on both sides of the stick.

At a previous place we set up a cluster on AWS. This was before EKS. We started out with kops initially but later used the generated CFN yaml. It was not an easy feat. There was a lot of gotchas, moving pieces and much more. All of these moving pieces had their own gotchas. Plus lots of competition in the area with not a lot of comparisons since it was early days. Many things were not fully stable. A lot of issues. We got there in the end, but it wasn't easy.

On the flip side, we were able to onboard people with their services in days, not weeks (previously the company ran their own datacentres). Teams were allowed to go to AWS directly, or go to our K8s cluster. I was able to observe the lead time of 3 teams, 2 chose k8s, 1 chose AWS. Those going to K8s were able to get their prod environment running within a week. The other team took a month to do their dev environment. All three teams deployed a single stateless service.

This is obviously anecdotal, but I was really impressed with the user friendliness of kubernetes for the consumers.

Nowadays, 4 years later at my current company, it's a different story with every major provider managing the clusters for you. At my current company we haven't taken the jump yet, so unfortunately I can't fully compare, but the little I've played with EKS, it's as easy as simple crud operations.

Post reply on HN