VPC Service Controls support for Cloud Scheduler jobs has been extended to Google Cloud APIs that are VPC Service Controls-compliant. For more information, see Secure cron jobs with VPC Service Controls.
]]>Support for Cloud Scheduler to call the following resources internally is in GA:
VPC Service Controls support for Cloud Scheduler jobs with the following targets is now in GA:
To learn more, see the documentation on how to secure cron jobs with VPC Service Controls.
]]>Support for Cloud Scheduler to call the following resources internally is in Preview:
VPC Service Controls support for Cloud Scheduler jobs with the following targets is now in Preview:
To learn more, see the documentation on how to secure cron jobs with VPC Service Controls.
]]>Support for using VPC Service Controls with Cloud Scheduler is now generally available (GA). To get started, check out the documentation on how to secure cron jobs with VPC Service Controls.
]]>Cloud Scheduler jobs that are paused can now be edited. See Create and configure cron jobs.
]]>Cloud Scheduler jobs for HTTP or Pub/Sub Targets can be deployed in multiple GCP Regions around the world and no longer require that an App Engine application be deployed.
]]>Cloud Scheduler is now available in us-west1, asia-east1, and asia-southeast1.
The Cloud Scheduler Console UI now has support for three additional options:
The maximum job size (payload) is now 1 MB total, including ~1KB request overhead.
]]>Two new headers, X-CloudScheduler-JobName and X-CloudScheduler-ScheduleTime, have been added to the default headers for AppEngineHttpTarget and HttpTarget. These can be used to help with job deduplication.
]]>Cloud Scheduler GA release.
]]>Cloud Scheduler Beta release.
]]>