341–350 of 633 posts
This makes GKE pretty much impossible to use for side projects. Given that it will cost $100 per cluster per month without including the instance costs. Edit: A single zonal cluster per GCP account is exempt from this fee, so this comment is inaccurate.
Earlier quoted context omitted.
$3600/year is significant for a startup on a shoestring budget.
So ask for Google cloud for startups? One free cluster is enough to get started.
This makes it seem like Google Cloud for Startups is aimed at startups that aren't really on a shoestring budget.
Oh wow, one of the biggest reasons we picked Google Cloud was that you did not have to pay a flat fee for their managed Kubernetes service. Luckily there is Kubernetes support across all Cloud Providers so we're happy we're not vendor locked in. (biggest reason we picked Kubernetes in the first place.) We were thinking of using Stackdriver for logging, but we were scared of vendor locked in due to price increases or…
Stackdriver is terrible, and super expensive for what it is. We ran a dedicated Fluentd in GKE for a long time to work around its shortcomings (GKE also uses/used Fluentd to shuffle logs into Stackdriver), then switched to using Loki + Promtail + Grafana, which has been excellent.
Earlier quoted context omitted.
> 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…
Hmm - have you considered a tool like Terraform or Deployment manager for creating the clusters? In general, it's best practice to capture that configuration as code.
You provide a web interface, so it’s reasonable to assume people will use it.
Earlier quoted context omitted.
Hey Seth, Thanks for being the recipient of everyone's (justifiable) frustrations. They probably don't pay you enough. I think, what is especially frustrating about this, is that we do already pay for resources that are provisioned by our K8S clusters. We pay for the network traffic, the storage, the compute. I saw you mention StackDriver... we pay for that as well. I can appreciate that actually setting up and manag…
> They probably don't pay you enough. Can confirm :) > ...we do already pay for resources that are provisioned by our K8S clusters Customers are charged for worker nodes, but until this point, the control plane ("master") nodes have been free. In addition to the raw compute costs for those nodes, there's the SRE overhead for managing, upgrading, and securing them. > ...but I generally assumed that that cost was amort…
This seems like a really important detail. For hobby projects, one cluster in one zone should be enough. Per your statement, those people will not be impacted. With this knowledge, I'm experiencing much less FUD.
Earlier quoted context omitted.
Less than 15 employees. Several products, two teams, We migrated our stuff from DigitalOcean around 2018. At the time, we briefly toyed with the notion of self-hosting Kubernetes on DO, but it's complex to manage, and we don't have any dedicated ops staff. GKE is significantly easier to manage. At that time we migrated, the things you mentioned weren't available/mature, I think. Even today, I'd choose Kubernetes over…
But DigitalOcean has managed K8s now: https://www.digitalocean.com/products/kubernetes/
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 .
This change is pretty huge for non-revenue units & small teams at institutions and SMBs. These smaller teams often seem to run two clusters rather than try to split their production and dev environments within one cluster (I think this is even widely recommended for smaller, less experienced outfits). For many the management fee will probably be a large percentage cost increase for units that are very cost sensitive…
Earlier quoted context omitted.
If the main value of GKE over DIY is $73, you should totally DIY. I mostly try not to be too Google-focused here, but I have to say... I'm pretty proud of GKE, and I think it offers a lot of value other than just being cheap. Managing clusters is not always easy. GKE handles all of that for you - including integrations, qualifications, upgrades, and patching clusters transparently BEFORE public security disclosures h…
Just a data point: I'm the CTO at a very small company. All our stuff is running on GKE. Our monthly bill tends is a lot less than $10,000/mo. We're currently in the process of splitting our stack into separate projects and clusters, because co-locating projects in a single cluster has gotten messy. We'll probably end up with 4-5. That will increase our bill by $292/mo, worst case, assuming the first cluster is free.…
You might not be at the scale where this is feasible yet since that's probably multiple full-time engineers, but eventually the cost functions intersect.
Earlier quoted context omitted.
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.
We need MySQL 8 because of window functions, which GCP does not offer. That is available on AWS.