Live data from Hacker News

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

cloud.google.com

31–40 of 633 posts

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

#31
I run a hobby project in multiple zones because low latency is important, and Kubernetes makes it easy to do so.

There's no way I'm going to pay an extra $73/mo -- I already pay for the computing resources, this should be free.

Looks like I'll be moving away from GKE. It's a shame, I _was_ a big advocate.

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

#32
post #15

That's about $72 a month, which matches Amazon EKS's lowered pricing. I guess that rules out my hopes of EKS not charging for the management plane in the near future.

It looks like Google's offering one free cluster per billing account if I read that right. If that's not the case, I'll be turning off my cluster before this kicks in.

One zonal cluster per billing account is free

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

#34

Time to dump GCP then. It's not even that the fee is that large, but rather that this is once again Google failing on a long term commitment and shafting those on their platform once again. This was one of the benefits that was pushed by their sales team when they called us up to market GCP over AWS and their EKS offering. Doesn't matter that they are price matching, Google's inability to actually commit to long term…

Thank you for the feedback. > Google's inability to actually commit to long term support... This is _exactly_ what Google is doing in this case. We are providing an SLA - a legal agreement of availability and support. These changes introduce a guaranteed availability of the management control plane.

Sure, in this case I can see that. I was referring to those four points with respect to Google services in general. I'm sure I don't need to dig up a list of features and services that have been merged, shuttered, price hiked or moved into a different product suite over the years. Admittedly a lot of the issues are with the GSuite side of things, but it's sad to see this coming to GCP as well.

On a hopefully more constructive note, if this is the way it's going to be from now on, I would at least expect to see an exemption on such a management fee/SLA on preemptible nodes - having an SLA and management fee on the cluster whereby nodes can be killed in a 30 second window without prior warning seems to be a little more than pointless.

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

#37

Time to dump GCP then. It's not even that the fee is that large, but rather that this is once again Google failing on a long term commitment and shafting those on their platform once again. This was one of the benefits that was pushed by their sales team when they called us up to market GCP over AWS and their EKS offering. Doesn't matter that they are price matching, Google's inability to actually commit to long term…

Thank you for the feedback. > Google's inability to actually commit to long term support... This is _exactly_ what Google is doing in this case. We are providing an SLA - a legal agreement of availability and support. These changes introduce a guaranteed availability of the management control plane.

He means that there was a sales pitch from all gcp sales guys to not charge for that. 99.95% is not enough IMO to charge 73$/mo.

As someone else noted, it breaks a lot of recommended architectures where you would have auto provisioning and a lot of clusters to separate concerns and keep costs down.

Finally, the pricing changes are starting to look like a pattern, every time Google deems the usage of a product is good enough, they will increase the price.

They are the Ryanair of the cloud.

Edit 1: moreover, it will increase the cost of composer, and on top of that, the recommended pattern where composer is paired with a kubernetes cluster for executing the workloads

Post reply on HN