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

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

cloud.google.com

Post reply on HN
Print view View original

241–250 of 633 posts

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

#241

Post by thockingoog »

GKE_Greed wrote: post #231
thockingoog wrote: post #228

Earlier quoted context omitted.

Google and Google Cloud are largely different businesses, though I understand it's hard to keep that in mind in the context of things like this. I encourage everyone to always stay nimble and keep your eyes on portability. I also encourage you to try to assess the REAL costs of doing things yourself. It's rarely as cheap as you think it is. As a Kubernetes maintainer, I am fanatical about portability. As part of the…

sorry that you have to work with such low-IQ people that made this decision. Followed your work on k8s, thank you, its better because of people like you and others.

I don't think that is at all a fair characterization, you just don't have the same data available to you.

Thanks for the props. It means a lot to me personally.

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

#243

Post by numbsafari »

sethvargo wrote: post #226
numbsafari wrote: post #133

Earlier quoted context omitted.

Hey Seth, Thanks for being the recipient of everyone's (justifiable) frustrations. They probably don't pay you enough. I think, what is especially frustrating about this, is that we do already pay for resources that are provisioned by our K8S clusters. We pay for the network traffic, the storage, the compute. I saw you mention StackDriver... we pay for that as well. I can appreciate that actually setting up and manag…

> They probably don't pay you enough. Can confirm :) > ...we do already pay for resources that are provisioned by our K8S clusters Customers are charged for worker nodes, but until this point, the control plane ("master") nodes have been free. In addition to the raw compute costs for those nodes, there's the SRE overhead for managing, upgrading, and securing them. > ...but I generally assumed that that cost was amort…

Thank you for the detailed response.

> In addition to the raw compute costs for those nodes, there's the SRE overhead for managing, upgrading, and securing them.

By that logic, can we expect to see charges for GCP Projects and the GCP Console? Cloud IAM?

> people have created many zero-node clusters

I'd be really curious what is driving folks to do that. Are they using the backplane for CRDs and custom controllers and no compute?

This feels like it could be addressed similar to alpha clusters, or with a quota, e.g.: clusters with 0 nodes for > 24 hours will be terminated?

Separately, It seems like handing everyone 3 months to figure out what to do about a new $73 * X fee isn't the best plan. Including some kind of estimate in the emails that were sent out would have been helpful. There was a change in pricing for StackDriver a while back that did this. It was very helpful to understand how we would be impacted.

> Furthermore, each billing account gets one zonal cluster with no management fee.

My feedback is that you would probably get getting way less blowback if that free-tier didn't come across as inadequate. I can appreciate that there are use-cases where it makes sense for you all to be charging. But one zonal cluster... It makes the whole thing feel punitive.

> I'm not sure what you mean by that verb.

I have a feeling we're all about to go on a journey of discovery together.

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

#244

Post by notyourday »

riyadparvez wrote: post #199
taleodor wrote: post #121

Earlier quoted context omitted.

My approach with any Google b2b product - always have a plan to migrate out of Google and never agree to anything that locks you to Google. After seeing what they did to Google Maps and Api.AI / Dialogueflow jumped from free to 5k$ overnight - just can't trust them.

> never agree to anything that locks you to Google. How is Google different from other cloud poviders in terms of vendor lock-in?

Being locked into a provider that does not increase prices or modify services in a non-compatible way ( cancel etc ) works much better than being locked into a provider that does.

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

#245

Post by [deleted] »

uberduper wrote: post #208
rolleiflex wrote: post #79

Earlier quoted context omitted.

We’re in the same situation — we’ve engineered for minimum provider-specific dependencies but GKE LoadBalancers were where they got us via arm twisting as well. There is no way to expose a cluster to the outside world in a production environment otherwise.

There are ways to expose your cluster to public and/or run your own load balancers on GKE (or any other cloud k8s deployment).

[deleted]

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

#246

Post by JMTQp8lwXL »

I've been mentioning Google's penny pinching for awhile here. Simple things like Chrome's address bar showing google searches before my bookmarks. It's all part of the monetization. Are fees like this because Google is struggling to continue to grow? That's probably the most concerning thing for Google's future, rather than a $73 fee.

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

#247

Post by partiallypro »

etchalon wrote: post #33

Time to start looking into DigitalOcean more seriously. G Cloud is already unreasonably expensive and nearly impossible to price manage. It's cool to see them double-down on that.

Outside of just hating Microsoft...why not Azure?

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

#248

Post by ratherbefuddled »

I don't like the direction this is heading, it seems like the SLA and the accompanying charge could easily have been optional.

We have a couple of dozen clusters, two per client, and can't change the architecture. We use helm and terraform and can build new clusters quickly but we can't treat them entirely like cattle because we don't own all the DNS. Our clients are not the sort to do things quickly - or even slowly.

Does anybody have any good and up to date resources comparing the current options for K8 providers? I'd like to get a feel for what it would take to switch.

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

#250

Post by dastx »

rolleiflex wrote: post #58

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…

For comparison, running a HA master node in London on n1-standard-1 will set you back ~93 dollars per month. On top of that obviously you'd be figuring out how Kubernetes works, what the best configuration is among other things. I don't agree with the blatant bait and switch, but it still works out way better.
Post reply on HN