41–50 of 633 posts
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.
https://news.ycombinator.com/item?id=20064169 https://news.ycombinator.com/item?id=17225665
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.
DO is pretty famous for losing data. https://news.ycombinator.com/item?id=20064169 https://news.ycombinator.com/item?id=17225665
$72/month per cluster, regardless of the size. It's interesting they're not charging per managed node (outside of the regular machine cost), makes it steep if you want to have a small cluster up.
Each billing account gets 1 free zonal cluster so the cost for keeping a small cluster up won't change.
Earlier quoted context omitted.
Shouldn't that be opt-in? The management control plane is not something we consider critical to operations. I'd happily accept if it was unavailable for 1 and a half minutes a day versus these additional costs.
That's great feedback. I'll relay that to the product team. IANAL, but I think it would be legally challenging.
And having it opt-in will save face with those users of GKE where an additional $73/m is significant.
Hey everyone - Seth from Google here. Please let us know if you have any questions! You can learn more about the pricing changes at https://cloud.google.com/kubernetes-engine/pricing .
Why is this change coming in? I can hardly see costs on Google's side having increased to provision and 'manage' K8S having increased over the past 3 years, especially given that it's used in production there. Also, given that no-cost K8S clusters was pushed by your sales and marketing teams back in 2018 as a significant benefit for switching to GCP, it doesn't really inspire confidence in GCP if we're just going to…
To your point about running your own K8S cluster - two things:
1. That's something you have always been (and still are) entitled to do.
2. Having personally run large-scale K8S clusters, the challenge isn't provisioning, it's maintenance, security patches, upgrades, etc.
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.
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…
What? A 73$ price difference to AWS was their main selling point?
250 * 0.1 * 1000 = $25,000/month.
This is quite the price hike for something that was a) free until now. b) Not a service that warrants such a fee given that it uses existing (GCE) resources and can frankly be done manually by one of the DevOps engineers for a few hours/month and some scripting. It's just a charge for convenience it seems.
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.
I think this is fair : for hobbyists, a free zonal cluster is sufficient and you probably wouldn't use more than one cluster. For businesses/revenue drivers, the $7.30/mo/cluster is nothing (EDIT: actually $73/mo/cluster, which may be a tougher sell but if the business is in a case where it benefits from Kubernetes, it's still likely insignificant relative to the cost of actually running the VMs on it )