This page lists GCP services that work well with Cloud Run and those that are not-yet supported for the fully managed version of Cloud Run. Cloud Run on GKE can use any service that Google Kubernetes Engine can use.
Connecting to GCP services in code
You can use Cloud Run (fully managed) with the supported GCP services using the client libraries they provide. For code samples showing how to connect with a particular GCP service, refer to the documentation provided for that GCP service.
You do not need to provide credentials manually inside Cloud Run (fully managed) container instances when using the GCP client libraries.
Note that Cloud Run (fully managed) uses a default runtime service account that has the Project > Editor role, which means it is able to call all GCP APIs and have read and write access on all resources in your GCP project. You can restrict this by assigning a service account with a minimal set of permissions to your Cloud Run services. For example, if your Cloud Run service is only reading data from Cloud Firestore, we recommend assigning it a service account that only has the Firestore User IAM role.
Services and tools recommended for use
The following table lists services recommended for Cloud Run (fully managed). These services also work well with Cloud Run on GKE, but in addition, Cloud Run on GKE can use any service that Google Kubernetes Engine can use.
|Cloud Build||Build container images, continuous integration and delivery.|
|Container Registry||Store container images.|
|Stackdriver||Monitoring and logging of Cloud Run services.|
|Cloud Firestore||Fully managed NoSQL database.|
|Cloud Storage||Object storage.|
|Cloud Pub/Sub||Push events to Cloud Run services. Refer to the Using Cloud Pub/Sub with Cloud Run Tutorial.|
|Cloud Scheduler||Trigger Cloud Run services on a schedule.|
|Cloud Tasks||Execute asynchronous tasks on Cloud Run. Refer to HTTP Target tasks with authentication tokens.|
|Identity Platform||Login your users.|
|BigQuery||Fully managed cloud data warehouse for analytics.|
|Firebase Hosting||Fully managed hosting service for static and dynamic content with configurable CDN caching.|
|Cloud Endpoints||API management including routing, authentication, API keys, rate limiting, and quota. Refer to Getting Started with Endpoints for Cloud Run.|
Connecting to Cloud SQL
Services not yet supported
The following table lists services that are not yet supported by Cloud Run (fully managed). Note that Cloud Run on GKE can use any service that Google Kubernetes Engine can use.
|Virtual Private Cloud||Cloud Run (fully managed) cannot connect to VPC network.|
|Cloud Memorystore||Cloud Run (fully managed) cannot connect to VPC network.|
|Cloud Filestore (NAS)||Cloud Filestore is not Cloud Firestore, which is supported.|
|Cloud Load Balancing|
|VPC Service Controls|
|Cloud Asset Inventory|