42 karma · joined November 11, 2018
And having it opt-in will save face with those users of GKE where an additional $73/m is significant.
I hope GCP re-thinks this.
- Spaces throwing up errors that magically fix itself a couple of days later.
- Asking about the credits we were promised for when Spaces lost our files results in the question being ignored. Still haven't received the promised credits for 6+ months. I can't even look back at the tickets now as the support system has deleted all the tickets older than a month.
It's gotten to the point where we have started work on migrating off DO, which is unfortunate because DO's offerings looked very attractive.
The interesting thing is that a couple of minutes before everything went wrong, kubectl returned a "error: You must be logged in to the server (Unauthorized)" error
I have seen some reports of Cloud pub/sub not working.
What Cloudflare needs is further customization, especially in regards to caching. We actually had to migrate a certain part of our infrastructure to Fastly due to the lack of caching customization/rules.
I'd like to see:
- Custom caching rules similar to the new firewall rules
- Finer granularity of the cache expiry (I'm aware Enterprise has the ability to cache for 30 seconds, but we don't want to upgrade to Enterprise just for that one thing).
- Cache hit rate analytics grouped by path/domain/etc
Edit: Source that says he graduated at Ethiopian https://www.nytimes.com/2019/03/12/business/ethiopian-airlin...
Does this mean we actually run the container ourselves on our GKE cluster or in a VM? Or do you mean a "container" runtime for Cloud Functions? Both would be interesting, but we'd prefer the latter since there would be less to manage. I'd be interested to see the performance of it.
Maybe even just something for compiled languages like Go, Crystal, etc that will just run the binary?
Would like to see some more runtimes/languages. I'm hoping AWS' recent layers implementation has made this more of a focus at Google. I'm curious how the implementation of Go has affected the ease of integrating other languages.
The timeline of this disruption matches when we started experiencing cloud build errors.