PERMISSION_DENIED(7): HTTP status code 403 when calling Cloud Run [190252876]

Assigned

Feature Request

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Jun 5, 2021 08:50PM

Problem you have encountered

When I configure a task to call an internal Cloud Run service, the task ends up getting PERMISSION_DENIED(7): HTTP status code 403

What you expected to happen

Cloud Tasks should be able to call internal services, thus offering better security defaults by allowing people to operate their queue workers as private services.

Comments

cr...@google.com <cr...@google.com> #2Jun 8, 2021 08:07AM

I also experience a high number of 502 in europe-west1

[Deleted User] <[Deleted User]> #3Jun 8, 2021 01:17PM

We suspect that we may be running into some sort of rate limit. The Cloud Tasks API Quota for maximum requests per minute is rather high (6 million/min) and we're not even close to that, but we believe that when we have bursts of task creation that the API then throws the 502.

cr...@google.com <cr...@google.com> #4Jun 9, 2021 10:09AM

Any update on this? It seems to be happening again. We are experiencing both high latency and 502, the requests are seconds apart.

ll...@google.com <ll...@google.com> Jun 21, 2021 09:04AM

Assigned to gc...@google.com.

be...@google.com <be...@google.com> #5Mar 9, 2022 10:51PM

Hi team - do we have update/ timeline we can report back to customers on this? Australia Post customers view on this is that it is a bug and not a feature request.

be...@google.com <be...@google.com> #6Mar 23, 2022 10:51AM

Comment has been deleted.

Message last modified on Mar 23, 2022 10:51AM

be...@google.com <be...@google.com> #7Apr 27, 2022 09:29PM

Hi team - gentle nudge on this please. Thanks

ma...@mova.vc <ma...@mova.vc> #8Jun 8, 2022 06:02PM

Hi, this problem was solved? I take this today. Thanks!

si...@metro-external.digital <si...@metro-external.digital> #9Sep 13, 2022 02:58PM

Hi, we also wanted to make use of Cloud Tasks for Cloud Run. But the fact that it does not work with internal ingress is very frustrating and not working out for us.. there is indeed a need to make it possible to integrate with internal Cloud Run services.

ky...@gmail.com <ky...@gmail.com> #10Sep 22, 2022 12:59AM

I second this, can we please get this!

ne...@blackkite.com <ne...@blackkite.com> #11Oct 4, 2022 03:23PM

Any progress on this topic?

yw...@xmatters.com <yw...@xmatters.com> #12Oct 7, 2022 04:40PM

Still not solved?

ad...@benvgroup.com <ad...@benvgroup.com> #13Nov 13, 2022 01:09PM

I am also struggling with this problem. My Cloud Scheduler always returns PERMISSION_DENIED for any trigger I create pointing to a Cloud Run Job.

md...@ford.com <md...@ford.com> #14Feb 22, 2023 01:05PM

i am also facing the same issue. somebody can please help me?

ja...@toteat.com <ja...@toteat.com> #15Mar 20, 2023 10:27PM

Hello, facing the same issue still, is there a timeline for this?