Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Kubernetes Engine's third consecutive day of service disruption

status.cloud.google.com

Post reply on HN
Print view View original

281–290 of 419 posts

Re: Google Kubernetes Engine's third consecutive day of service disruption

#281

Post by dpark »

vira28 wrote: post #261
navinsylvester wrote: post #193

Earlier quoted context omitted.

We are GCP customers for the last couple of years. We use other cloud platforms(AWS, IBM, Oracle, OrionVM) too. We don't use GKE but use rancher/kubernetes combo on their standard platform. So far GCP is the best, hands down in terms of stability. We never had a single outage or maintenance downtime notification till now. We are power users but our monitoring didn't pick any anomaly so i don't think this issue had ra…

I use AWS free tier and get customer support through email, but thats not the case with GCP. Do they provide free email support? If you are an early stage startup can you afford their 200/Month support, when your entire GCP bill is under $1. However, that doesn't mean you don't have to support them.

If 200/month is an issue, then you aren’t an “early stage startup”. You’re running a hobby project.

Re: Google Kubernetes Engine's third consecutive day of service disruption

#282

Post by ty_a »

greglindahl wrote: post #276
ernsheong wrote: post #254

Earlier quoted context omitted.

As if something like this has never happened to AWS?

"like this" -- a failure of the service, or a failure of communication and customer support?

Remember that time S3 went down and the only updates were on Twitter because the status page was hosted on S3?

Re: Google Kubernetes Engine's third consecutive day of service disruption

#283

Post by [deleted] »

dpark wrote: post #281
vira28 wrote: post #261

Earlier quoted context omitted.

I use AWS free tier and get customer support through email, but thats not the case with GCP. Do they provide free email support? If you are an early stage startup can you afford their 200/Month support, when your entire GCP bill is under $1. However, that doesn't mean you don't have to support them.

If 200/month is an issue, then you aren’t an “early stage startup”. You’re running a hobby project.

[deleted]

Re: Google Kubernetes Engine's third consecutive day of service disruption

#284

Post by jjeaff »

jkaplowitz wrote: post #209
scoot wrote: post #157

Earlier quoted context omitted.

> To me that looks like a reasonable deprecation policy. It might be, until they jack up the prices 15X with limited notice (looking at you, Google maps [1]). No deprecation needed, just force users off the platform unless they're willing to pay a massive premium. [1] https://www.google.com/search?q=google+maps+price+increase

Google Maps has never been subjected to that policy, unlike GCP services. These org chart divisions are real but only clear to Googlers, Xooglers (I'm in this category), and people who pay extremely close attention. The fact that they're all Google makes reputation damage bleed across meaningfully different parts of what's in truth now a conglomerate under the umbrella name Google.

Except all the Google maps setup and API keys are generated from the gcp UI and the billing happens on the cloud platform as well. While maps didn't start as a gcp product, they seem to have rolled it in to gcp fully.

Re: Google Kubernetes Engine's third consecutive day of service disruption

#285

Post by ascar »

ty_a wrote: post #282
greglindahl wrote: post #276

Earlier quoted context omitted.

"like this" -- a failure of the service, or a failure of communication and customer support?

Remember that time S3 went down and the only updates were on Twitter because the status page was hosted on S3?

I don't. But thanks for sharing, that's hilarious (for an unaffected person at least :D)

Re: Google Kubernetes Engine's third consecutive day of service disruption

#286

Post by pzh »

ty_a wrote: post #282
greglindahl wrote: post #276

Earlier quoted context omitted.

"like this" -- a failure of the service, or a failure of communication and customer support?

Remember that time S3 went down and the only updates were on Twitter because the status page was hosted on S3?

The S3 outage duration was only 4 hours.

Re: Google Kubernetes Engine's third consecutive day of service disruption

#287

Post by devonkim »

scarface74 wrote: post #106
user5994461 wrote: post #100

Earlier quoted context omitted.

The baseline is that it takes 12 dedicated people across the world to run a 24/7 support operation. Considering that even tech companies hardly manage to have a pair of DevOps or Sysadmin, running one own infrastructure is completely out of question.

Most small companies on AWS with revenue outsource support to an MSP.

Any stats / surveys on this? Most smaller (< 50 employees) b2c enterprise-style SaaS companies I'm anecdotally familiar with barely have enough funds to hire ops engineers let alone outsource to MSPs (even if the MSP practices labor rate arbitrage). A lot of the criteria I'd wager may be conditions around pre-revenue status and funding conditions moreso than headcount. I'm trying to understand just how biased my own experiences and indirect experiences are with the wider US market and appreciate data.

Re: Google Kubernetes Engine's third consecutive day of service disruption

#288

Post by housingpost »

joshuamorton wrote: post #160
chrisseaton wrote: post #152

Earlier quoted context omitted.

But what do these things mean? > commercially reasonable > substantial economic or material technical burden Is one engineer working on an old service to keep it alive commercially reasonable or a substantial burden? I don't know. Do you? In practice this policy lets them shut off anything they want any time they want. Again it's their playground they can do what they want unless they signed a contract saying they'd…

I think you're ascribing an unreasonable amount of bad faith here, and, to rephrase what I had here before, you're approaching this from an engineering perspective, not a legal one. And that's not how those things work. To be clear, that policy is a contract. And those things would be decided by a jury. And if my understanding is correct, the reasonable person standard applies. So you can answer this yourself, do you…

I’d say google earned that bad faith this year alone with what they did with maps.

Re: Google Kubernetes Engine's third consecutive day of service disruption

#289

Post by joshuamorton »

housingpost wrote: post #288
joshuamorton wrote: post #160

Earlier quoted context omitted.

I think you're ascribing an unreasonable amount of bad faith here, and, to rephrase what I had here before, you're approaching this from an engineering perspective, not a legal one. And that's not how those things work. To be clear, that policy is a contract. And those things would be decided by a jury. And if my understanding is correct, the reasonable person standard applies. So you can answer this yourself, do you…

I’d say google earned that bad faith this year alone with what they did with maps.

As another user mentioned, maps isn't cloud.

Re: Google Kubernetes Engine's third consecutive day of service disruption

#290

Post by illumin8 »

hacknat wrote: post #52

Question to Google employees: Why do you guys suffer global outages? This is your 2nd major global outage in less than 5 years. I’m sorry to say this, but it is the equivalent of going bankrupt from a trust perspective. I need to see some blog posts about how you guys are rethinking whatever design can lead to this - twice - or you are never getting a cent of money under my control. You have the most feature rich clo…

Google has a global SDN (software-defined network) that gives them some unique and beneficial capabilities, like being able to onboard traffic in the closest CDN POP and letting it ride over the Google backbone to the region your systems are running in.

The problem is that running a global SDN like this means if you do something wrong, you can have outages that impact multiple regions simultaneously.

This is why AWS has strict regional isolation and will never create cross-region dependencies (outside of some truly global services like IAM and Route 53 that have sufficient redundancy that they should (hopefully) never go down).

Disclaimer: I work for AWS, but my opinions are my own.

Post reply on HN