Site Logo
Sivamuthu Kumar
Published on

Google Cloud Run - Add Persistent Storage


Hello 👋 , In part 1 of the Google Cloud Run series, we learned what Google Cloud Run is, how to deploy the source code or container to the Google Cloud Run, and set up the continuous deployment to deploy the application to Cloud Run using a few clicks set up in the portal. In this part 2 of the series, let's see the options available to add persistent storage to the Cloud Run applications. At the end of this blog post, you will learn to add persistent storage into the python flask application.

Google Cloud Storage

Google provides various storage options that address various needs of your applications. This post will explain the three storage options to integrate into your application running in Google Cloud Run

  1. Cloud SQL - Storing Structured Data
  2. Cloud Firestore - Storing Unstructured Data
  3. Cloud Storage - Storing files such as images and video

Cloud SQL - Storing Structured Data

Cloud SQL is a fully managed database service that helps you set up, maintain, manage, and administer your relational databases in the cloud. You can configure MySQL, PostgreSQL, SQL Server - RDS in the Cloud SQL. In this, we will create a MySQL instance that can be accessed from the Private IP address. And connect the Cloud SQL instance in the Google Cloud Run.

gcloud sql instances create cloud-sql-demo \
--database-version=MYSQL_8_0 \
--memory=MEMORY_SIZE \
--network # Private IP Address

Once the Cloud SQL is provisioned, you can add the connections to Cloud Run services and configure the VPC Access connector in the Portal or using gcloud cli

gcloud compute networks vpc-access connectors create CONNECTOR_NAME \
--network VPC_NETWORK \
--region REGION \
--range IP_RANGE

gcloud run services update SERVICE --vpc-connector CONNECTOR_NAME


Please refer to Connecting to Cloud SQL from Cloud Run (fully managed) for detailed documentation on how to set up managed Cloud SQL connection with Cloud Run.

Connect the CloudSQL Database providers using sqlalchemy library by configuring the database host, port, database and credentials.

def init_tcp_connection_engine(db_config):
    db_user = os.environ["DB_USER"]
    db_pass = os.environ["DB_PASS"]
    db_name = os.environ["DB_NAME"]
    db_host = os.environ["DB_HOST"]

    # Extract host and port from db_host
    host_args = db_host.split(":")
    db_hostname, db_port = host_args[0], int(host_args[1])

    pool = sqlalchemy.create_engine(
    return pool

Let's create order data and store the order table.

@app.route("/order", methods=["POST"])
def create_order():
    data = request.get_json()
		item = data['item']
		requested_at = datetime.datetime.utcnow()

		stmt = sqlalchemy.text(
        "INSERT INTO orders (item, requested_at)" " VALUES (:item, :requested_at)"
        with db.connect() as conn:
            conn.execute(stmt, item=item, requested_at=requested_at)
    except Exception as e:
        return Response(
            response=jsonify({ error: "Unable to successfully cast vote! Please check the "
            "application logs for more details."  }),

    return Response(
        response=jsonify({ 'msg' : 'Order Created Successfully'}),

Google recommends that you use Secret Manager to store sensitive information such as SQL credentials. After setting up the secrets in the Secret Manager, you can update the env variables to update the secrets in Cloud Run.

gcloud run services update SERVICE_NAME \
--update-secrets=DB_USER=DB_USER_SECRET:latest \
--update-secrets=DB_PASS=DB_PASS_SECRET:latest \

Cloud Firestore - Storing Unstructured Data

Cloud Firestore is a flexible, scalable, NoSQL database for mobile, web, and server development from Firebase and Google Cloud. Following Cloud Firestore's NoSQL data model, you store data in documents that contain fields mapping to values. These documents are stored in collections, which are containers for your documents that you can use to organize your data and build queries. You can refer to this quick start to set up the Cloud Firestore.

Create a Cloud FireStore Client by initializing the app using firebase_admin package.

import firebase_admin
from firebase_admin import credentials
from firebase_admin import firestore

cred = credentials.ApplicationDefault()
firebase_admin.initialize_app(cred, {
  'projectId': project_id,

db = firestore.client()

Add the new order to the orders collection to store.

@app.route("/order", methods=["POST"])
def create_order():
    data = request.get_json()
		item = data['item']
		requested_at = datetime.datetime.utcnow()

		db_col = db.collection(u'orders');
		    u'item': item,
		    u'requested_at': requested_at

    return Response(
        response=jsonify({ 'msg' : 'Order Created Successfully'}),

Cloud Storage - Storing files such as image and video

You can use Google Cloud Storage to store the files such as images, videos, and other static content. We are using the Google Cloud Client Library to store files in Google Cloud Storage. The file content of the request is saved into the Cloud Storage blob and writes to the Cloud Storage bucket. Once the file is uploaded to Cloud Storage, the pubic URL to this file is returned, which you can serve to the file directly from Cloud Storage. You can store this URL in your data storage too.

import logging
import os

from flask import Flask, request
from import storage

CLOUD_STORAGE_BUCKET = os.environ["cloud_storage_bucket"]

@app.route('/upload', methods=['POST'])
def upload():
    """Process the uploaded file and upload it to Google Cloud Storage."""
    uploaded_file = request.files.get('file')

    if not uploaded_file:
        return 'No file uploaded.', 400

    gcs = storage.Client()

    # Get the bucket that the file will be uploaded to.
    bucket = gcs.get_bucket(CLOUD_STORAGE_BUCKET)

    # Create a new blob and upload the file's content.
    blob = bucket.blob(uploaded_file.filename)

    return blob.public_url


In this second part of the series, we explored the options to add Persistent Storage in Google Cloud Run. In the next part of the series, we will explore more on how to orchestrate a Workflow using Cloud Run & Cloud Functions, and in the final part of the series, we will see how to add Cloud Endpoints to the Cloud Run applications and build developer API portal.

I'm Siva - working as Sr. Software Architect at Computer Enterprises Inc from Orlando. I am going to write technical blogs on Cloud, Containers, IoT, and Devops. If you are interested in any of that, make sure to follow me if you haven’t already. Please follow me @ksivamuthu Twitter or check out my blogs at Please drop a comment below or reach me out if you've any questions or comments.