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

171–180 of 633 posts

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

#171

Post by andrewmutz »

rolleiflex wrote: post #90
sethvargo wrote: post #80

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.

Seth — I appreciate you being here to take feedback, and for the clarification as well. The very surprising email I’ve received this morning is very hazy on the details, and the docs linked from the email are not updated yet. The main issue is that not charging for the control plane and charging for the control plane leads to two very different Kubernetes architectures, and as per your docs, those decisions made at t…

If this cost bothers you a great deal, why not just deploy a new cluster?

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

#172

Post by Thaxll »

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.

DO is for garage projects. If you need anything serious it's AWS / GCP or MS.

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

#173

Post by croh »

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.

For last 7 years I am running DO and never had any issue. I never understand why it is looked down. In fact I have faced so many issues with AWS (particulary their old hardward). In one case, our ec2 instance was rebooting frequently. AWS team didn't accept any issue from there end and after few weeks ask us to upgrade instace because of bad health.

In my experience, AWS is a very expensive cloud with clunky UI and big brand name. During consulting gigs, I have seen many customers want to go with AWS only because of brand. And later they cry when bills start to hit roof with vendor lock in.

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

#174

Post by freedomben »

lazyier wrote: post #148
rolleiflex wrote: post #106

Earlier quoted context omitted.

That’s interesting - I think you’re right. We might move our staging cluster into our main production deployment. More likely though, AWS or OpenShift running on bare metal on a beefy ATX tower in the office. We want to have production and staging as close to each other as possible, so this is an additional reason and a p0 flag on reducing the dependency on Google-specific bits of Kubernetes as much as possible, hope…

Kubespray works well for me for setting up a bare bones kubernetes cluster for the lab. I'll use helm to install metallb for the load balancer, which you can then tie into whatever egress controller you like to use. For persistent storage a simple NFS server is the bees knees. Works very well and a NFS provisioned is a helm install. Very nice, especially, over 10GbE. Do NOT dismiss NFSv4. It's actually very nice for…

Have you used NFS for persistent storage in prod much? I know people do it, but numerous solutions architects have cautioned against it.

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

#175

Post by ones_and_zeros »

rolleiflex wrote: post #90
sethvargo wrote: post #80

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.

Seth — I appreciate you being here to take feedback, and for the clarification as well. The very surprising email I’ve received this morning is very hazy on the details, and the docs linked from the email are not updated yet. The main issue is that not charging for the control plane and charging for the control plane leads to two very different Kubernetes architectures, and as per your docs, those decisions made at t…

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?

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

#176

Post by the_duke »

marcinzm wrote: post #70
toomuchtodo wrote: post #53

Earlier quoted context omitted.

Why people think cloud providers are benevolent provider of infra is beyond me. Their margin is because people are willing to pay it. Either run your own metal (k8s arguably makes this easier than VMs along in the past) or form a cloud coop, but absolutely don't be shocked when a business is taking money off the table because they can. Don't marry yourself to a provider, stay portable, it's just good risk management.…

Different companies make money using different approaches and it's perfectly valid to be upset at the approach a particular company is taking. Just because they provide a service doesn't mean they'll try to f * you over at every chance. For some it's bad long term business to do that. AWS, for example, begins with high prices and then lowers them over time. It costs money but you know the maximum. Google seems to be…

> AWS, for example, begins with high prices and then lowers them over time. It costs money but you know the maximum.

That's only true for official pricing though.

I know of multiple cases where AWS had initially given significant discounts, only to stop doing so once they believed the customer to be firmly tied to the platform.

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

#177

Post by fcantournet »

londons_explore wrote: post #135

Are there any other companies doing managed Kubernetes in GCP? If there was interest I could try to build a third party clone of GKE running in all GCP regions and still managing GCP VM's, and I could run it for a lot less than $0.10 per hour (although obviously it would take many months of refinement till I could offer a decent SLA)

Canonical has an offer

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

#178

Post by mrbrowning »

lvh wrote: post #100
xur17 wrote: post #93

Earlier quoted context omitted.

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

This highlights a sorta-weird consequence of this pricing change: suddenly pricing incentivizes you to use namespacing instead of clusters for separating environments. (As a security person: ugh.)

I suspect I'm in the minority on this, but I would love for k8s to have hierarchical namespaces. As much as they add complexity, there are a lot of cases where they're just reifying complexity that's already there, like when deployments are namespaced by environment (e.g. "dev-{service}", "prod-{service}", etc.) and so the hierarchy is already present but flattened into an inaccessible string representation. There are other solutions to this, but they all seem to extract their cost in terms of more manual fleet management.

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

#180

Post by sethvargo »

outworlder wrote: post #166
dward wrote: post #108

Earlier quoted context omitted.

GKE can't offer financial backed SLOs without charging for the service. This is something that, I assume, significant customers want and that competitors already have: https://aws.amazon.com/eks/sla/

Workers are not free and never were. So they were already charging.

Correct, but the control plane nodes _were_ free and had no SLA. This changes that. [edit: spelling]
Post reply on HN