Google Brings Serverless Compute Load Balancer

Recently, Google announced support for serverless compute in Global HTTP(S) Load Balancing and CDN.
 
Google said that the new External HTTP(S) Load Balancing integration enables serverless offerings like App Engine, Cloud Functions and Cloud Run to use the same fully-featured enterprise-grade HTTP(S) load balancing capabilities as the rest of Google Cloud.
 Source: Google
 
This integration allows you to assign a single global anycast IP address to your service, manage its certificates and TLS configuration, integrate with Cloud CDN, and for Cloud Run and Functions—load balance across regions. In the next few months, the company will also add features like support for Cloud Identity-Aware Proxy (IAP) and Cloud Armor.
 
One of Google Cloud HTTP(S) load balancing's core features is load balancing across multiple, different backend types, and the integration of serverless NEGs improves on that. The load balancer’s URL map can now mix Serverless NEGs with other backend types.
 
 
Source: Google
 
Now, Cloud Run, Cloud Functions and App Engine can have Cloud CDN enabled just like a Cloud Storage bucket or non-GCP backend. Network engineers can use the HTTP(S) Load Balancer to route static traffic to their Cloud Storage bucket and their web users or API clients to their serverless backend. This allows you to make the most of the CDN.
 
 
Source: Google
 
In order to use Cloud CDN with your serverless origin you simply need to enable Cloud CDN on the backend service that contains your serverless NEG.
 
For additional details, you can visit the official announcement here.