Cloud Run + Firebase Hosting region rewrites issue

Question

I'm trying to use Firebase Hosting for CDN connected to Cloud Run. Yesterday I was testing something for region eu-west1 and it went well. Today I'm trying to do the same but for region eu-west4 and I'm getting error that this region is not supported. I switched to eu-west1 and it worked.

Is this bug or region eu-west4 is not supported?

=== Deploying to 'xxxxxxxx'...
i  deploying hosting
Error: HTTP Error: 400, Cloud Run region `europe-west4` is not supported.

    "rewrites": [
      {
        "source": "**",
        "run": {
          "serviceId": "web-client",
          "region": "europe-west4"
        }
      }
    ],

same for new asia-southeast1 region also

Error: HTTP Error: 400, Cloud Run region `asia-southeast1` is not supported.

Answer 1

From this info here is the Details information regarding Rewrite:

Firebase Hosting originates in us-central1 so while deploying cloud Run it's recommended to select us-central1 region for less First Contentful Paint score or quick loading of your website, but kills the advantage of your nearby region availability purpose(really unfortunate for google fanboys).

Example: if your location is India your nearest cloud run available is asia-southeast1 Singapore we can't select asia-southeast1

Request path would go like this:

you→India(CDN)→USA(Firebase)→Signapore(CloudRun+aync call to Firestore India)→USA→CDN→you (which is REALLY BAD in terms of latency).

you→India(CDN)→USA(Firebase)→USA us-central1(CloudRun+aync call to Firestore India)→USA→CDN→you

(static Page will Load FAST, but Firestore dynamic data on webapp will data load with REALLY BAD in terms of latency, we should select us-central1 for Firestore also this makes no use of your local region GCP products this really strange that Firebase hosting not available for at least for AMERICA EUROPE ASIA-PACIFIC zones atleast).

Conclusion(till this date):

Cloud Run region rewrites issue for Firebase Hosting is there for many regions but, for the optimal page load result we should select us-central1 it is really unfortunate THIS IS THE REAL PROBLEM compare to Rewrite Issue, to avoid website Firestore latency for non USA users we should use cloud run/cloud function cache control such that data will cached at your local/near by region CDN for fast data loading (we cant use firebase web SDK since CDN caching not possible via if we use SDK, we should use Cloud function in firebase/cloud run)

Firebase Hosting to Cloud Run rewrite availability ( as of Aug 31, 2020)

Available:

us-central1, us-east1, asia-northeast1, europe-west1

Not available asia-east1, europe-north1, europe-west4, us-east4, us-west1, asia-southeast1

Please file a feature request for Firebase rewrite availability if it's not available in your region Cloud Run and Firebase hosting not available for at least for AMERICA EUROPE ASIA-PACIFIC zones.

FYI: Cloud Firestore multi-region also not available for Asia region if using multi-region Firestore is the fix for locked Firebase hosting and Cloud run regions to us-central1

Cloud Run availability region

(Please comment if you get the rewrite access to any of the above mentioned region)