nickhsine
commented
2 years ago Since storytelling cloud run send request to Old Bucket can be successfully routed by VPC connector. Maybe the difference between the configuration of Old Bucket and New Bucket contains the root cause.
Does the cloud run request new bucket files provided by GCS (URL starts with https://storage.googleapis.com) successfully?
If there is no timeout issue for requesting new bucket files provided by GCS, then I am afraid that the root cause might not be the bucket configurations.
caesarWHLee
Define
Old Bucket: statics-editools-dev &cloudshell=false&project=mirrorlearning-161006&prefix=&forceOnObjectsSortingFiltering=false) New Bucket: editools-gcs-dev.readr.tw &cloudshell=true&project=mirrorlearning-161006&prefix&forceOnObjectsSortingFiltering=false)
Description
Since storyteling is Next.js structure and needs to rely on SSR data fetching to prevent hydrate error. And the page liveblog is based on the liveblog json file to render all the contents. So a request sent by storytelling server using
getServerSideProps.Fetching the json from the Old Bucket got no problem. But after switching to use the New Bucket by chaning the environmental variable
GCS_BUCKET_URL. The request always timeout and not able to get the liveblog json file.Follow-Up
From @nickhsine's observation: By the configuration of storytelling cloud run, all the egress requests will be routed through serverless VPC connector. Looks like request
https://editools-gcs-dev.read.tw/from storytelling cloud run will face the timeout issue.Workaround
Setting egress requests to Route only requests to private IPs through the VPC connector. => Only private ip/ internal dns will be routed through VPC connectorr
Old request flow: cloud run -> vpc connector -> gcp load balancer -> gcs
After workaround: cloud run — (internal ip/ internal dns) —> vpc connector -> gcp resources cloud run — (external ip/ external dns) —> internet --> external resources
In this configuration, when storytelling cloud run send request to
https://editools-gcs-dev.readr.tw. The request will be sent outside to the internet and then back to the gcp to prevent that VPC can't findhttps://editools-gcs-dev.readr.tw.Note
Since storytelling cloud run send request to Old Bucket can be successfully routed by VPC connector. Maybe the difference between the configuration of Old Bucket and New Bucket contains the root cause.