Earlier quoted context omitted.
No caching provided either. Full on egress charges. Surely that makes the comparison apples/oranges.
Caching is provided with GCP HTTPS load balancers, it’s just not specified here.
Google Cloud Armor
41–50 of 54 posts
Re: Google Cloud Armor
#42Re: Google Cloud Armor
#43Kubernetes doesn't support multi-region load balancing with GSLB yet.
How is that related to security policies? 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-…
Re: Google Cloud Armor
#44Not a huge fan of Google getting more control over the net. On the bright side, Cloudflare getting a serious competitor is good.
Agreed. I just wish it wasn't Google. They "extinguished" a lot of good projects...
Re: Google Cloud Armor
#45Re: Google Cloud Armor
#46Re: Google Cloud Armor
#47Re: Google Cloud Armor
#48Earlier quoted context omitted.
How is that related to security policies? 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-…
Running a Kubernetes cluster across multiple regions is not a great idea. You can set up a federation of clusters, but GKE doesn't seem to support that yet, so you need to create and manage the federated control plane yourself. And there's no standard way at the moment to have generic cross-cluster networking, like you easily could with Borg. So you can load balance external requests to a number of clusters, as you e…
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
Re: Google Cloud Armor
#49Re: Google Cloud Armor
#50Earlier quoted context omitted.
> Cloudflare is way too expensive. 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.)
Not comparing to Cloud Armor, but the $200/month minimum to bring one's own tls certificate. That alone puts Cloudflare squarely on the list of unusable options for any small project or business that is running their entire production infrastructure on less than $100/month. Also, the inability to specify cache expirations below... what was it... 30 minutes or 2 hours? Again, forced to pay too much for one of the core…