Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Apigee with target backend cloud run in internal ingress

Hello,

I have a backend service on CloudRun running with ingress=internal. This service is accessible through a VM in the same VPC. When i try to access it through Apigee (pay-as-you-go) that has been created in the same VPC i get a 404 not found. Is there any solution to get direct access without using and internal LB and PSC with Service attachment?

Solved Solved
2 9 1,871
2 ACCEPTED SOLUTIONS

You can increase the default 30 seconds timeout to the longest amount of time that your expect your psc backend to need in order to process a response.  For example:

gcloud compute backend-services update demo-psc-backend-service --global --timeout=31 --project=${PROJECT_ID}

 Alternatively you can also use the load balancer UX to update backend service timeout value.

View solution in original post

The UX and backend service resource showing 30 seconds as default is a known issue however the timeoutSec property is ignored for serverless NEG backends.

View solution in original post

9 REPLIES 9