Google Kubernetes Engine's third consecutive day of service disruption

Re:Google Kubernetes Engine's third consecutive day of servi... by totallyashill on Monday November 12, 2018 @03:14AM (#18431253)

Very similar thing at our office. Considering the scale of which we run things, any outage could be a potential loss of millions _every minute_.

Sure, we use support tickets with vendors for small things. Console button bugging out, etc. But for large incidents, every vendor has a representative within an hour driving distance and will be called into a room with our engineers to fix the problem. This kind of outage, with zero communication, means the dropping of a contract.

Communication is critical for trust, especially if we're running a business off it.

[ Parent | on HN ]

Re:Google Kubernetes Engine's third consecutive day of servi... by y4mi on Monday November 12, 2018 @11:33AM (#18433565)

Going single cloud on that scale is simply irresponsible though.

You need failovers to different providers and hopefully also have your hardware for general workloads

And suddenly the CEO doesn't care anymore if one of your potential failovers is behaving flaky in specific circumstances

Not saying it's good as it is.. communication as a saas provider is - as you said- one is the most important things... But this specific issue was not as bad as some people insinuate in this thread

[ Parent | on HN ]

Re:Google Kubernetes Engine's third consecutive day of servi... by softawre on Monday November 12, 2018 @12:16PM (#18433900)

Agree, if we are really talking about millions per minute (woah), then you can afford to failover to AWS.

[ Parent | on HN ]