Live data from Hacker News

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

cloud.google.com

571–580 of 633 posts

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

#571
Years ago, GKE had a $0.15/hr charge for clusters with more than 5 nodes. They dropped that and other clouds matched them. Now they're adding back a fee for all clusters.

Bringing back that original min cluster size would be a good idea and probably solve a lot of the issues with people running dev/stage clusters.

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

#572

Earlier quoted context omitted.

Hi Seth, What about clusters that are used for lumpy work loads? Like data science pipelines? For example, our org has a few dozen clusters being used like that. Each pipeline gets its own cluster instance as a way to enforce rough and ready isolation. Most of the times the clusters sit unused. To keep them alive we keep a small, cheap, preemptive node alive on the idle cluster. When a new batch of data comes in, we…

Those empty clusters that you get for free cost Google money. Perhaps it never should have been free, because that skewed incentives towards models like this.

Keep in mind that GKE cluster management was paid in the original GKE. GCP only stopped billing for cluster management when EKS released free cluster management.

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

#573
post #255

Earlier quoted context omitted.

If the main value of GKE over DIY is $73, you should totally DIY. I mostly try not to be too Google-focused here, but I have to say... I'm pretty proud of GKE, and I think it offers a lot of value other than just being cheap. Managing clusters is not always easy. GKE handles all of that for you - including integrations, qualifications, upgrades, and patching clusters transparently BEFORE public security disclosures h…

I believe everything that you say. The value it provides is very good. If Google Cloud would have charged 73$ from the start (or after beta), i think there wouldn't be so much anger. The anger comes from, a product was free and now it is not. A lot of people made architectural choices that depended on the price of 0. (You mentioned these cases in your post). However, i believe the bigger issue is, that Google Cloud b…

> However, i believe the bigger issue is, that Google Cloud broke essentially a promise.

Which promise?

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

#574

This is awful - I don’t think GCP is fully aware of their position in the market as the second, inferior choice. I took a bet on the underdog by using GCP and they bit me back in return. Especially considering their ‘default’ kubernetes config automatically sets you up with three(!) control planes in replication, that’s, as far as I understand, $~300 added to our monthly bill, for nothing. Oh, and per their docs, thr…

> I don’t think GCP is fully aware of their position in the market as the second, inferior choice

Aren't they the third choice, after AWS and Azure?

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

#575

Earlier quoted context omitted.

If there were a lower complexity way to deploy containerized apps supported widely I think tons of people would go for it. Currently there's not really much of a middle ground between Cloud Run and K8s offered. It's kind of absurd, honestly.

Google App Engine has been exactly this since 2008.

My impression of app engine is that you have to use all the cloud* services like SQL, cache, etc, which will make it significantly more expensive, even if it does that app layer fine. Is that wrong?

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

#577
post #86

Earlier quoted context omitted.

It's kind of ridiculous internal load balancers can't get automatic certs. We've had to do a stupid dance just to get certs via the LE DNS challenge out of band, and then regularly install them on internal LBs.

Maybe I don't understand your problem, but can't you just use Traefik ( https://docs.traefik.io/user-guides/crd-acme/ ). It will get certs from letsencrypt for you.

Key word: "internal" -- these aren't on the internet, Traefik does ALPN, which means the LB itself has to be on the Internet. (Or something else that leaks the cert to the LB, but that doesn't sound any less complicated than using the DNS challenge.)

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

#578

I guess I need to start migrating my clusters, then. $73 per cluster on my prod, dev, QA, and test clusters is a significant increase for me. Looks like Google is doing their best to kill off GCP - https://www.cnbc.com/2019/12/17/google-reportedly-wants-to-b...

Curious where you are going to go that is going to be cheaper for the management plane and work nodes.

AWS+kops is less expensive. Digital Ocean and Azure provide services without charging for master nodes.

I will likely choose AWS+kops.

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

#579

Earlier quoted context omitted.

Assuming you can do that, and your system is not using namespacing for its own purposes.

I know kubeflow can use namespaces for its own purposes, but otherwise I thought that was quite rare. Namespaces are intended to be used for exactly this usecase (isolating teams and/or workloads). What kind of system have you seen where this isn't true?

We've seen plenty of examples where people do this. Sometimes it's different teams (e.g. the ML team is namespaced away from the primary customer flow) and sometimes it's for different customers. Really, it sounds like we're in agreement about why this happens, the confusion is just whether or not that normally happens within a company in the course of doing business?

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

#580
post #564

Earlier quoted context omitted.

It's not about whether it's worth it. I have no idea if $73/mo/cluster is more or less than what GKE is worth, but you can't ignore the time-varying aspect of this change. If GCP had started at $100/mo and just announced a price drop to $73/mo, your customers would probably be cheering, even though you'd be charging them the same! They'd be happy about being loyal to you, thankful that your offering gets better over…

> Now doesn't seem like the time to pull unit margins up. Tbf, you don't have the data to say that. Maybe GCP hit the growth targets they had and are not interested in growing more; maybe they've grown so much that service quality is going down; maybe they want to stall and build up other parts of the offer... there are a lot of reasons why they might want to cash in. Whether they could have foreseen it happening at…

> Maybe GCP hit the growth targets they had and are not interested in growing more; maybe they've grown so much that service quality is going down; maybe they want to stall and build up other parts of the offer...

No, they are on a death march for market share. https://www.crn.com/news/cloud/google-reportedly-set-ambitio...

Post reply on HN