Instance failed to start because permission was denied when creating an address in the subnetwork

[Klaitos]

Hello,

Am I the only one experiencing recent issue when deploying new revisions with the following error :

`Instance failed to start because permission was denied when creating an address in the subnetwork xxx in the VPC network. Please check IAM settings.` 

I'm using Cloud Run direct vpc egress feature and I did not update IAM configurations recently.

The issue is not permanent and does affect some revisions randomly.

The issue appeared for the first time the 2024-06-18.

[Abdellatif051]

Hello, I have the same problem,

https://stackoverflow.com/questions/78646518/cloud-run-instance-failed-to-start-because-permission-w...

I have been using Direct VPC egress in google cloud run since May 2, 2024 to access to Cloud SQL via private IP in the same network. I have 2 environnments prod and staging, same configurations except min-instances (1 in prod and 0 in staging)

Since June 18 I have been receiving these errors (only in staging) when the number of instances remains 0 for more than 20 minutes. (Only for the first request, in other cases works well)

Instance failed to start because permission was denied when creating an address in the subnetwork, Please check IAM settings.

Even though I assigned the networkUser role to the cloud run service agent.

[llay]

I have the same issue
EDIT: Just redeployed `

gcloud run deploy my-app --project=<project-id> --image <image> --region us-west1` and did not experience the issue again