Support for http endpoints on compute instances without public ip [154867787]

Assigned

Feature Request

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Apr 24, 2020 10:37AM

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:

ability to trigger HTTP endpoints on compute engine machines without the public IP
while keeping ability to keep all scheduled jobs in one place/UI.

How this might work:

UI/api to define network and project on which http job will be invoked.
or ability to specify project region and instance as we do for IAP tunnels in gcloud utility.

If applicable, reasons why alternative solutions are not sufficient:

Other information (workarounds you have tried, documentation consulted, etc):

Comments

mu...@google.com <mu...@google.com> #2May 6, 2020 03:15AM

Assigned to gc...@google.com.

Hello Ervin,

An internal feature request has been opened on your behalf concerning your request for Cloud Scheduler to add support for http endpoints on GCE instances without public IP.

Our feature requests do not have an ETA nor a guarantee they will be implemented in the near future.

Any updates to this feature request will be made here.

jc...@gmail.com <jc...@gmail.com> #3Mar 24, 2021 01:29PM

I would like to see this too. Scheduler support for a gce-internal ingress private ipaddress.

ka...@sabre.com <ka...@sabre.com> #4Jun 16, 2021 11:05AM

Hi ,

I have opened the below case for this requirement of "Cloud Scheduler to add support for http endpoints on GCE instances without public IP"

https://console.cloud.google.com/support/cases/detail/27973259

This is very much needed for DST schedules.

As a workaround, we are defining 6 jobs (K8s CronJobs) per schedule like [summer-begin, summer-middle, summer-end, winter-begin, winter-middle and winter-end] just to manage DST.

If any of our customer wants a new schedule, then it has become so difficult to maintain schedules with plain K8s.

Will be awaiting for an update on the feature....

gb...@wideorbit.com <gb...@wideorbit.com> #5Oct 25, 2021 09:46AM

Any fix on above issue ?

fa...@gmail.com <fa...@gmail.com> #6Feb 11, 2022 11:25PM

Would love to see this feature!

er...@doit.com <er...@doit.com> #7Mar 3, 2022 04:49PM

Customer is requesting this capability to enhance the usability of this service throughout their fleet.
Specifically, routing of http requests through internal GCP network before moving externally. This way internal hostnames can be used to target instances for scheduling.

Message last modified on Mar 3, 2022 04:51PM

yo...@pipl.com <yo...@pipl.com> #8May 17, 2022 01:48PM

need this feature too

er...@pactum.com <er...@pactum.com> #9Jun 3, 2022 10:23AM

I would also link an ability to call Cloud Run http endpoints which have private-only-ingress as it is very similar issue - Cloud Scheduler needs to be "attachable" to VPC connector to appear local to VPC, accessing all resources, not just compute engine machines.

ka...@google.com <ka...@google.com> #10Nov 11, 2022 12:28PM

I have a Cx with similar Cloud Scheduler issue - He is using Cloud Scheduler to integrate with Cloud Run URL but getting permission denied error and is not able to send full auth token.

Product - Cloud Scheduler
Vector Case Link -

https://vector.lightning.force.com/lightning/r/Case/5004M00000vQSnXQAW/view
Can you please provide further insights and any fix for this issue?

ju...@gmail.com <ju...@gmail.com> #11Nov 16, 2023 01:03AM

Workaround: Use Cloud Scheduler to trigger a Cloud Run Job. A Cloud Run Job can be connected to a VPC and it can send HTTP requests to Compute Engine VMs that have only a private IP address.