Ah, the sound of former Oracle executives counting their GCP bonuses.
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.…
Google Kubernetes Engine is introducing a cluster management fee on June 6
111–120 of 633 posts
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#112This 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…
GCP is actually more the 3rd inferior option, behind Azure. Gartner lists Azure as just behind AWS for IaaS providers, and GCP a more distant 3rd: https://pages.awscloud.com/Gartner-Magic-Quadrant-for-Infras...
Also lack of SLA / shady SLA does not help.
Ps. Talking as someone with hands on experience.
Ps2. Azure support is terrible and their response times are constantly breaking SLA..
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#113Earlier 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…
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#114Earlier quoted context omitted.
I'm sorry to hear that. You can use namespaces and and separate node pools to isolate workloads. We'd love to hear more about your use case for having many small GKE clusters.
Hey Seth, I know you used to work at Hashicorp on vault. I think Vault recommends that if you want to deploy it on Kubernetes, it should have the cluster to itself.
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#115This 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…
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#116Here is a very good tutorial on how to set up your own cluster: https://community.hetzner.com/tutorials/install-kubernetes-c...
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#117This 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…
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.
That feels like the wrong attitude.
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#118Earlier quoted context omitted.
Same goes for metal, your data center can suddenly increase your prices massively or go bankrupt.
For sure! That's why I said, "Don't marry yourself to a provider, stay portable". Compute is a commodity, treat it as such.
For a startup, the risk of AWS doing something is tiny compared to all other risks so not worth spending effort to mitigate.
For a moderately sized company, true, being on multiple clouds may have an advantage.
For a large company, you get long term contracts with AWS that mitigate the risk.
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#119Earlier quoted context omitted.
GCP is actually more the 3rd inferior option, behind Azure. Gartner lists Azure as just behind AWS for IaaS providers, and GCP a more distant 3rd: https://pages.awscloud.com/Gartner-Magic-Quadrant-for-Infras...
Anecdotal, I know, but for prospective Latacora customers this is absolutely not reflected in market share. It's AWS first, GCP second, Azure very distant third. I'd happily believe Azure is dominating in some segments where MS showers prospective customers with millions of dollars in credit, but IMO a blind person can see Azure does not have the product offering to warrant a "completeness of vision" that is right on…
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#120Earlier 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…
Sorry for technical tangent but curious. Your decision making on GCP appears to appeal to best of breed + cost. But you put SQL Server on AWS? If you are saying SQL Server is better on AWS than on Azure it would be interesting to learn why.