IANAL either, but I don't see why it would be? Just have a separate cluster type, e.g SLA Zonal, SLA Regional. The SLA already differentiates the current cluster types. Anthos Clusters are also not subject to any additional fees?
And having it opt-in will save face with those users of GKE where an additional $73/m is significant.
Shouldn't that be opt-in? The management control plane is not something we consider critical to operations. I'd happily accept if it was unavailable for 1 and a half minutes a day versus these additional costs.
I've been using DO spaces for about a year now, and for the later half of that time, my experience has been pretty terrible.
- 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.
I happened to be initializing a GKE pool upgrade just as this occurred. The upgrade is now stuck according to the console.
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'm having issues with the GCP console, but all our GCP services are working without issue. Lots of errors related to spanner popping up in the console.
I have seen some reports of Cloud pub/sub not working.
I'm a big supporter of Cloudflare and have been using it for almost 8 years. I personally don't think doing something like that is what Cloudflare needs.
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
> running a container that could be run like Cloud Functions
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.
We've used GCF for some production tasks and it's worked pretty well for us.
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.
Seems to be some weird underlying issue going on at GCP at the moment. Had cloud build webhooks returning a 500 error. Noticed we were at 255 images and deleting some fixed the issue. Created a P2 ticket about the issue before we managed to solve it and haven't had a response in 40+ hours.
The timeline of this disruption matches when we started experiencing cloud build errors.