Using Cloud Tasks with VPC network [154481516]

Assigned

Feature Request

Status Update

No update yet.

Description

ik...@google.com

created issue #1

Apr 20, 2020 12:39PM

Currently it is not possible to connect to any resource from Cloud Tasks by using VPC networks. The current workaround is by authenticating users to perform the specific actions by adding roles/permissions to them.

So it is wanted to have this functionality as it is a security method that could avoid some security issues that might affect production as well.

Comments

gs...@mandmdirect.com <gs...@mandmdirect.com> #2Apr 20, 2020 01:08PM

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

bo...@google.com <bo...@google.com> #3Apr 20, 2020 01:52PM

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.

tt...@thai.run <tt...@thai.run> #4Oct 12, 2020 04:23PM

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

br...@cannonballtrading.com <br...@cannonballtrading.com> #5Jul 28, 2021 02:44PM

+1 - repeating everything previous post said

[Deleted User] <[Deleted User]> #6May 6, 2022 05:56PM

+1 we would like to be able to point cloud tasks to our internal dev pods

ma...@bestbuy.com <ma...@bestbuy.com> #7Jun 10, 2022 05:44PM

Having problems with attempting to invoke Cloud Function that has allow internal only settings from a Cloud Task. Surprised this feature still hasn't be created 2 years later it would go a long way in allowing Cloud Task to have easy usage for our Cloud Resources on an enterprise level. Not really any work arounds for us.

[Deleted User] <[Deleted User]> #8Jun 29, 2022 08:29PM

I feel very uncomfortable exposing some important data endpoints only for cloud tasks to access it, all other services are available on private network, this should be a priority on security to enable this configuration

ca...@gmail.com <ca...@gmail.com> #9Aug 30, 2022 03:15AM

After more than two years, is there any update on the progress here?

co...@lucemhealth.com <co...@lucemhealth.com> #10Sep 21, 2022 07:32PM

Any update on this?

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

Any update on this?

ra...@jagesar.org <ra...@jagesar.org> #12Oct 19, 2022 03:57PM

Any update on this?

ca...@gmail.com <ca...@gmail.com> #13Oct 20, 2022 01:27AM

For anyone following this issue, I believe the answer here would also apply. Someone from the team can correct me if I'm wrong, though. Sounds like this is rolling out in preview now, and is expected to be released fully before the ended of the year.

ch...@appchoose.io <ch...@appchoose.io> #14Nov 16, 2022 11:10AM

It seems to be in general availability since 15th of november, didn't tried yet.

da...@google.com <da...@google.com> #15Nov 16, 2022 08:16PM

Thought I'd give an update on this bug as well. Cloud Tasks can now target Cloud Functions and Cloud Run with VPC-SC or using internal-only ingress. We are working on adding support for VPC private IPs as well in 2023.

ka...@searce.com <ka...@searce.com> #16Jan 26, 2023 04:32AM

Any updates on adding the support for VPC private IPs ?

jo...@meplan.com.au <jo...@meplan.com.au> #17Mar 6, 2023 12:07PM

Can Cloud Tasks now call App Engine services that have internal and load balancer ingress?

le...@shine.fr <le...@shine.fr> #18Apr 24, 2023 02:17PM

va...@google.com <va...@google.com> Apr 25, 2023 06:15AM

Reassigned to ku...@google.com.

je...@zonarsystems.net <je...@zonarsystems.net> #19Jun 22, 2023 06:57PM

would love to have the ability to send a task to an API via internal ingress as we don't want the API to be public

ku...@google.com <ku...@google.com> Jul 4, 2023 08:30AM

Assigned to ku...@google.com.

ku...@google.com <ku...@google.com> Jul 6, 2023 05:37AM

Reassigned to gc...@google.com.

dm...@wayfair.com <dm...@wayfair.com> #20Aug 4, 2023 08:10AM

ga...@glean.com <ga...@glean.com> #21Aug 16, 2023 08:56PM

+100 can you add VPC support to Cloud Tasks similar as Cloud Functions/Run, allowing it to connect to VPC endpoints either via a VPC connector or direct VPC egress?

gu...@gohighlevel.com <gu...@gohighlevel.com> #22Mar 12, 2024 03:27PM

+1 to add this feature

Sending the API requests to workloads via internet will add more security concerns

om...@dave.com <om...@dave.com> #23Jul 9, 2024 04:20PM

Comment has been deleted.

Message last modified on Jul 9, 2024 04:20PM

om...@dave.com <om...@dave.com> #24Jul 9, 2024 04:21PM

+1 to add this feature

pe...@telus.com <pe...@telus.com> #25Sep 19, 2024 07:53PM

Comment has been deleted.

Message last modified on Sep 19, 2024 09:47PM

in...@kellner4you.app <in...@kellner4you.app> #26Dec 23, 2024 11:30AM

+1 to add this feature

kb...@ueat.io <kb...@ueat.io> #27Feb 12, 2025 01:30PM

+1 to add this feature. Really cumbersome and unsecure to open external door for things that can be internal. Do you plan something for that? It's opened since 2020...

je...@gmail.com <je...@gmail.com> #28Feb 12, 2025 02:07PM

Not sure why this is still open: I have been using Cloud Tasks to push to Cloud Run inside a VPC for some time now.

Issue 154481516

Description

Issue summary

Comments

gs...@mandmdirect.com <gs...@mandmdirect.com> #2Apr 20, 2020 01:08PM

bo...@google.com <bo...@google.com> #3Apr 20, 2020 01:52PM

tt...@thai.run <tt...@thai.run> #4Oct 12, 2020 04:23PM

br...@cannonballtrading.com <br...@cannonballtrading.com> #5Jul 28, 2021 02:44PM

[Deleted User] <[Deleted User]> #6May 6, 2022 05:56PM

ma...@bestbuy.com <ma...@bestbuy.com> #7Jun 10, 2022 05:44PM

[Deleted User] <[Deleted User]> #8Jun 29, 2022 08:29PM

ca...@gmail.com <ca...@gmail.com> #9Aug 30, 2022 03:15AM

co...@lucemhealth.com <co...@lucemhealth.com> #10Sep 21, 2022 07:32PM

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

ra...@jagesar.org <ra...@jagesar.org> #12Oct 19, 2022 03:57PM

ca...@gmail.com <ca...@gmail.com> #13Oct 20, 2022 01:27AM

ch...@appchoose.io <ch...@appchoose.io> #14Nov 16, 2022 11:10AM

da...@google.com <da...@google.com> #15Nov 16, 2022 08:16PM

ka...@searce.com <ka...@searce.com> #16Jan 26, 2023 04:32AM

jo...@meplan.com.au <jo...@meplan.com.au> #17Mar 6, 2023 12:07PM

le...@shine.fr <le...@shine.fr> #18Apr 24, 2023 02:17PM

va...@google.com <va...@google.com> Apr 25, 2023 06:15AM

je...@zonarsystems.net <je...@zonarsystems.net> #19Jun 22, 2023 06:57PM

ku...@google.com <ku...@google.com> Jul 4, 2023 08:30AM

ku...@google.com <ku...@google.com> Jul 6, 2023 05:37AM

dm...@wayfair.com <dm...@wayfair.com> #20Aug 4, 2023 08:10AM

ga...@glean.com <ga...@glean.com> #21Aug 16, 2023 08:56PM

gu...@gohighlevel.com <gu...@gohighlevel.com> #22Mar 12, 2024 03:27PM

om...@dave.com <om...@dave.com> #23Jul 9, 2024 04:20PM

om...@dave.com <om...@dave.com> #24Jul 9, 2024 04:21PM

pe...@telus.com <pe...@telus.com> #25Sep 19, 2024 07:53PM

in...@kellner4you.app <in...@kellner4you.app> #26Dec 23, 2024 11:30AM

kb...@ueat.io <kb...@ueat.io> #27Feb 12, 2025 01:30PM

je...@gmail.com <je...@gmail.com> #28Feb 12, 2025 02:07PM

Add comment

Issue metadata