[1] But I did find this page about their network research: https://research.google.com/teams/netsys/
Http load balancers already log all requests. Security policies decisions will also be logged, but in preview mode won't actually affect the traffic.
EDIT: looks like advanced rules are in alpha for only certain customers...
Google are very good at internet plumbing, and I expect this to be a pretty compelling service. Serious competition and not being an acquisition target any more must have really hurt Cloudflare's value today.
Of course, for those who are already using GCP and depending on their needs is a great alternative.
* Theano -> TF
* The multitude of RSS readers -> Google Reader
* Severely undermined Firefox
* Usenet newsgroups -> Google GroupsPolicy Charge $5 per Cloud Armor policy per month Per Rule Charge $1 per rule per policy per month Incoming Requests Charge $0.75 per million HTTP(S) requests
Eh? DDoS protection on Cloudflare is free: https://blog.cloudflare.com/unmetered-mitigation/
Which features of Google Cloud Armor are "too expensive" with Cloudflare?
(Disclosure: I'm an engineer at Cloudflare, but I'm genuinely curious what you mean here.)
Personally I use Cloudflare's free tier for lots of projects, and it has a perfectly reasonable TLS offering.
If you need that kind of technical details than Cloudfront or Stackpath are pretty good for low traffic sites.
Google’s model de facto means they’re just running another protection racket, that is they make more money the more DDoS attacks there are.
From Azure’s website:
> Protection against unplanned costs
> Our cost protection provides service credits for resource costs which are incurred as a result of a documented DDoS attack.
Also you can't run a GKE cluster across multiple regions, only multiple zones. If you have multiple clusters in different regions, you can use a NodePort service on each and manually setup a GSLB with a backend pointing to all of the GKE clusters.
There is a solution being worked on though, called multi-cluster ingress: https://github.com/GoogleCloudPlatform/k8s-multicluster-ingr...
GKE doesn't support federation because it's not a final feature either, it was beta at best and is now being revised and renamed to "multi-cluster": https://github.com/kubernetes/community/tree/master/sig-mult...
If you need to reach services between clusters, that's completely different from ingress. Ingress is about external access to cluster services.
You can still use an authentication layer and expose everything through an ingress, or use internal IPs for the services/containers which are already routable in GCP's network across regions. A headless service to get the IPs and a cron job to sync these to a public DNS system will give you the same thing federation does for cross-cluster service discovery. There are also apps like ExternalDNS that'll do it for you: https://github.com/kubernetes-incubator/external-dns
Fastly was good for technical setups but Cloudflare Workers blows away Varnish VCL config.
Not sure if this would work better.