4 ms·
Google cloud support is PATHETIC. We had a production Kubernetes outage caused by a bug in Google Cloud. We were paying for gold level support. They deescalat
by _zskd 8y ago
Google cloud support is PATHETIC.
We had a production Kubernetes outage caused by a bug in Google Cloud. We were paying for gold level support.
They deescalated and reescelated our ticket 3 times.
In the end they closed the ticket and sent me a link to "Architecting distributed application" docs. I think they were trying to be condescending. That idiot should have been canned.
Eventually I threw a big fit in the Google Cloud slack channel and thockin ended up looking at the issue and finding the bug.
- sandGorgon 8y agoThere's a Google cloud slack channel? Can you link ?
- fitzoh 8y agohttps://gcp-slack.appspot.com https://gcp-slack.appspot.com
- dstroot 8y agoTim Hockin is my freakin hero.
- thockingoog 8y agoLOL. Thanks for the shout out. I am sorry you had a bad experience. Please be assured that we are working on it, and that we take this seriously.
- honkycat 8y agoIf I may be so bold, where should I direct this complaint so that people hear it: When you delete a CloudSQL instance, it also deletes the back-ups associated with that instance along with it. There is also no way to mark a CloudSQL instance as "protected" so one bad keypress can lose you your production database and all backups. This is... cartoonishly dumb. Clownish. - Cloudsql instance deletion protection should exist - Those backups should be preserved somewhere when I delete the instance.
- sandGorgon 8y agoagreed - backups have nothing to do with an instance. i should be able to spin up and down postgresql instances, but backups should be stored (and billed) as per cloud storage rates.