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

621–630 of 633 posts

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

#621

Post by redis_mlc »

dralley wrote: post #505
buzzkillington wrote: post #301

Earlier quoted context omitted.

The projects I've been on that used GCP over AWS fell into two categories. 1). CEO with delusions of grandeur who thought that Amazon was a direct competitor to their business and should not be given money. 2). Projects that used Kubernetes. Two is the only type of project which doesn't result in tens of millions of dollars wasted.

> 1). CEO with delusions of grandeur who thought that Amazon was a direct competitor to their business and should not be given money. I mean, look at Netflix.

Netflix chose AWS because it was the only viable cloud at the time. (They used Azure for backups.)

In fact, Netflix helped build AWS. There were daily long-term scheduled meetings with AWS developers to review new features and versions.

In addition, the policy from mgmt. was that they were fine being mono-cloud, since if they changed their mind, they had the engineering resources to migrate whenever it made sense.

Source: worked at Netflix.

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

#622

Post by ygggvg »

diegoperini wrote: post #537
ygggvg wrote: post #85

Earlier quoted context omitted.

It's 72$ not 300 and the first is free. I'm not sure what your usecase is that you would choose gke and you are worried about 300$ per month infra costs. For Corp we use gke. For private I use selfhostet k3samd for our startup asuper cheap digital ocean cluster.

$300 is more than minimum wage in some countries.

Context is critical. You should be able to get my context. We are not sitting around a fire somewhere nowhere. We are discussing things on hn.

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

#623

Post by pbalau »

fluuuhi wrote: post #551
ak217 wrote: post #488

Earlier quoted context omitted.

Both AWS and Google offer free tier products and pay-for-what-you-use products. Reserved instance pricing starts at around $25/year. Many other incredibly useful products (S3, Lambda, VPC, etc.) are free with an instance or start at $0. You can set billing alerts that will project your monthly budget every hour, and send you an alert when it's projected to be exceeded. IMHO your claim (that there is an entry cost bar…

My main concern is, that i can't define an upper limit. My billing alert is nice and im aware of it, but it doesn't help you if someone takes over your account, mines bitcoins on expensive machines and a day later you read your email.

AWS has budgets that do exactly what you want. For the "cost budget": "Monitor your costs against a specified dollar amount and receive alerts when your user-defined thresholds are met."

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

#625

Post by bluhbi »

rolleiflex wrote: post #145
sethvargo wrote: post #129

Earlier quoted context omitted.

Thank you These changes won't take effect until June - customers won't start getting billed immediately. I'm sorry that you feel trapped, that's not our intention. > You should keep existing clusters in the pricing model they’ve been built in, and apply this change for clusters created after today. This is great feedback, but clusters should be treated like cattle, not pets. I'd love to learn more about why your clus…

> This is great feedback, but clusters should be treated like cattle, not pets. I'd love to learn more about why your clusters must be so static. What’s inside our clusters are indeed cattle, but the clusters themselves do carry a lot of config that is set via GCP UI for trivial things like firewall rules. Of course we could script it and automate, but your CLI tool also changes fast enough that it becomes an ongoing…

Right now with k8s it is definit a 'ongoing maintenance'. We allocate around 0.5-2 pt per week on only doing that. If we would not do that, most of our stuff would be already outdated.

I know already too many people which are stuck at a certain k8s version. Do not allow that to happen!

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

#626

Post by ratherbefuddled »

vpEfljFL wrote: post #556
ratherbefuddled wrote: post #404

Earlier quoted context omitted.

> As many have mentioned here already, $72/mo most likely a rounding error on workloads kubernetes is designed for. There are _many_ reasons to use k8 beyond just workload scale and that amount per cluster per month isn't anywhere near a rounding error for many deployments.

I would be interested to know when you may need kubernetes for small types of workload and simple architecture. For my understating, support contract alone for google cloud will cost you around $150/mo. For small to medium workloads there are plenty of tools if you want to use containers: docker swarm and nomad. Docker Swarm is really simple and most engineers already know it because of `docker-compose.yml` they're u…

One simple example - of many: Enterprise clients with low workload but very sensitive data strict infosec and segregation requirements - several clusters per client all managed with infrastructure as code.

There are lots of benefits to k8 other than just scale, and there are architecture choices that are made for good reasons that rely on separate clusters with no particular need for a legal uptime SLA on a control plane.

This decision will cost us a lot more than $72 a month.

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

#628

Post by nikolay »

justlexi93 wrote: post #502

A very basic truth that AWS understands is that you introduce a product at price X, and then either keep it at X or reduce the price moving forward. You never, ever, EVER increase prices on established products. You also basically never discontinue products, even if there's only a handful of customers still using it (ex: SimpleDB). Apparently it's just too tempting to Google management to juice revenue in the short t…

Google is the worst product management company. Being the GCP, they don't really care, but this will move many SMBs to DigitalOcean.

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

#629

Post by aludwin »

mrbrowning wrote: post #602
aludwin wrote: post #238

Earlier quoted context omitted.

Hey - I'm a member of the multitenancy working group (wg-multitenancy). We're working on a project called the Hierarchical Namespace Controller (aka HNC - read about it at http://bit.ly/38YYhE0 ). This tries to add some hierarchical behaviour to K8s without actually modifying k/k, which means we're still forced to have unique names for all namespaces in a cluster - e.g., you still need dev-service and prod-service. B…

Hey, thanks for asking! My interests in it are primarily for quota management -- in my experience, this is inevitably a hierarchical concern, in that you frequently run into the case of wanting to allot a certain cluster-wide quota to a large organizational unit, and similarly subdivide that quota between smaller organizational subunits. Being able to model that hierarchy with namespaces localizes changes more effect…

Thanks! We're not currently planning on implementing a hierarchical resource quota in HNC, but HNC is trying to define a definition of hierarchy that could certainly be used to create a HRQ. Give me a shout if you're interested in contributing.

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

#630

Post by dserodio »

sethvargo wrote: post #129
rolleiflex wrote: post #90

Earlier quoted context omitted.

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…

Thank you These changes won't take effect until June - customers won't start getting billed immediately. I'm sorry that you feel trapped, that's not our intention. > You should keep existing clusters in the pricing model they’ve been built in, and apply this change for clusters created after today. This is great feedback, but clusters should be treated like cattle, not pets. I'd love to learn more about why your clus…

Thanks for replying to feedback Seth. Stuff like this - following the Google Maps API massive pricing increase, the G Suite pricing increase - is what makes me wary about building stuff on GCP: I'm afraid that Google will increase prices for stuff I rely on. AWS has made users expect pricing for cloud services to only go down.
Post reply on HN