Live data from Hacker News

Google Kubernetes Engine is introducing a cluster management fee on June 6

cloud.google.com

291–300 of 633 posts

Re: Google Kubernetes Engine is introducing a cluster management fee on June 6

#291
post #223

Earlier quoted context omitted.

Which axe are you grinding? If you took this personal then maybe something stuck because it should? If you mean there is no cussing allowed then I missed that for sure. Edit: ah checked your history. So you say things like "Amazon reviews are about as trustworthy as the selling points of a slimy salesman" thus impugning Amazon and salespeople in general but are coming after me because you are no doubt personally miff…

Welcome to HN - this is not reddit - please take a look at the comment rules: https://news.ycombinator.com/newsguidelines.html

LOL! Did you read them??

"Please don't submit comments saying that HN is turning into Reddit. It's a semi-noob illusion, as old as the hills."

Likening HNN to reddit and posting that like you did is the definition of "snarky" IMO.

Please grind your axe in the open over the content instead of appeal to alleged community norms you are fine violating.

Re: Google Kubernetes Engine is introducing a cluster management fee on June 6

#293
post #93

Earlier quoted context omitted.

Thank you for the feedback. The management fee is per cluster. You are not billed for replicated control planes. You can use the pricing calculator at https://cloud.google.com/products/calculator#tab=container to model pricing, but it should work out to $73/mo regardless of nodes or cluster size (again, because it's charged per-cluster). There's also one completely free zonal cluster for hobbyist projects.

We currently spin up dev clusters with a single node. $73/mo is going to basically double the cost of all of these..

Generally curious, isn’t Docker Kubernetes an option?

Re: Google Kubernetes Engine is introducing a cluster management fee on June 6

#294
post #41

Earlier quoted context omitted.

DO is pretty famous for losing data. https://news.ycombinator.com/item?id=20064169 https://news.ycombinator.com/item?id=17225665

DO is famous for being a pain in the ass. They’re great for tiny hobby things but honestly I’d never run a prod/serious/client workload there. Too many issues. I’ve had multiple clients lose a droplet due to a simple credit card expiration. It’s a race to the bottom on price so this doesn’t surprise me. They chose this life.

Why would you use the cloud but have that single point of failure? Billing is also a network activity. Why not have the backup infrastructure linked to another credit card?

Re: Google Kubernetes Engine is introducing a cluster management fee on June 6

#295
I know the HN crowd hates this sort of thing, but seems reasonable to me. $70/month is a very reasonable price, and most businesses likely have well under 10 clusters (I’d think many just have 2-3, a single cluster for prod and then 1-2 dev/test type environments). This is probably mostly to cut down on edge cases users who are spinning up crazy numbers of clusters for weird reasons, and costing Google a bunch of $$$.

Re: Google Kubernetes Engine is introducing a cluster management fee on June 6

#296

Earlier quoted context omitted.

I agree the rollout is a little bumpy but I'm curious what workloads you are using k8s for where a $74/mo (or $300/mo) bill isn't a rounding error in your capex?

$3600/year is significant for a startup on a shoestring budget.

So ask for Google cloud for startups? One free cluster is enough to get started.

Re: Google Kubernetes Engine is introducing a cluster management fee on June 6

#297

I don't offhand remember AWS increasing prices for a service before but I might be wrong. How often does Google increase prices? For a business I prefer a company that starts with higher prices and then only lowers them to one that may increase them at any time.

Having worked for AWS, one of the things we got a lot push back from was offering something free and then walk back from it.

AWS really strongly focuses on gaining customer trust, and they will only lower price, and never increase price. They won't turn off things until the last customer stops using it (they might stop new customers from onboarding)

I did not enjoy working for AWS so I left pretty fast, but some of the customer obsession there really impressed me.

Re: Google Kubernetes Engine is introducing a cluster management fee on June 6

#298
Just got this email. $0.10 per hour is so much for something that was 0 per hour before. Wow these guys. The chutzpah! This isn’t just offensive monetarily, it’s offensive like price gouging is offensive. It’s emotionally offensive. Gotta look somewhere else. Shame.

Re: Google Kubernetes Engine is introducing a cluster management fee on June 6

#299
post #295

I know the HN crowd hates this sort of thing, but seems reasonable to me. $70/month is a very reasonable price, and most businesses likely have well under 10 clusters (I’d think many just have 2-3, a single cluster for prod and then 1-2 dev/test type environments). This is probably mostly to cut down on edge cases users who are spinning up crazy numbers of clusters for weird reasons, and costing Google a bunch of $$$…

Furthermore, anyone spending enough on compute to warrant k8s shouldn’t balk at all at $70/mo. I think the threshold for introducing the complexity and overhead of k8s isn’t probably until at least $5-10k/mo of spend (and probably 3-10x that in the normal case). Less than that and k8s is a whole lot of overkill.

Re: Google Kubernetes Engine is introducing a cluster management fee on June 6

#300
post #197

Oh wow, one of the biggest reasons we picked Google Cloud was that you did not have to pay a flat fee for their managed Kubernetes service. Luckily there is Kubernetes support across all Cloud Providers so we're happy we're not vendor locked in. (biggest reason we picked Kubernetes in the first place.) We were thinking of using Stackdriver for logging, but we were scared of vendor locked in due to price increases or…

Stackdriver is terrible, and super expensive for what it is. We ran a dedicated Fluentd in GKE for a long time to work around its shortcomings (GKE also uses/used Fluentd to shuffle logs into Stackdriver), then switched to using Loki + Promtail + Grafana, which has been excellent.
Post reply on HN