<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Batch on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/batch/</link><description>Recent content in Batch on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 21 Jul 2026 12:20:39 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/batch/index.xml" rel="self" type="application/rss+xml"/><item><title>GCP Batch enforces job-location constraint by July 31, 2026</title><link>https://curadevops.metacog.co.kr/insights/2026-07-21-july-20-2026/</link><pubDate>Tue, 21 Jul 2026 12:20:39 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-21-july-20-2026/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Act:&lt;/strong> GCP Batch will reject jobs whose &lt;code>allowedLocations[]&lt;/code> field lists regions or zones outside the job&amp;rsquo;s own location; the deadline is July 31, 2026 for most projects (June 30, 2027 for projects that already submitted a cross-region job before that date). Audit all Batch workloads for cross-region &lt;code>allowedLocations[]&lt;/code> entries and restrict them to the job&amp;rsquo;s location before July 31, 2026.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>