<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cost on brtkwr.com</title><link>https://brtkwr.com/tags/cost/</link><description>Recent content in Cost on brtkwr.com</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 15 May 2026 05:26:23 +0000</lastBuildDate><atom:link href="https://brtkwr.com/tags/cost/index.xml" rel="self" type="application/rss+xml"/><item><title>Avoiding Cloud NAT cost for Artifact Registry image pulls</title><link>https://brtkwr.com/posts/2026-05-15-avoiding-cloud-nat-cost-for-artifact-registry-image-pulls/</link><pubDate>Fri, 15 May 2026 05:26:23 +0000</pubDate><guid>https://brtkwr.com/posts/2026-05-15-avoiding-cloud-nat-cost-for-artifact-registry-image-pulls/</guid><description>&lt;h2 id="tldr">
 TL;DR
 &lt;a class="heading-link" href="#tldr">
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
 &lt;span class="sr-only">Link to heading&lt;/span>
 &lt;/a>
&lt;/h2>
&lt;p>A private GKE cluster&amp;rsquo;s outbound traffic to &lt;code>*.googleapis.com&lt;/code> and &lt;code>*.pkg.dev&lt;/code> flows through Cloud NAT by default and pays $0.0385/GB data processing on every byte, in both directions. The GCP UI says &amp;ldquo;Private Google Access is in effect&amp;rdquo; for the subnet, which makes it sound like that traffic already bypasses NAT. It does not. To bypass NAT for Google API traffic, I added a private Cloud DNS zone resolving the Google API hostnames to the &lt;code>restricted.googleapis.com&lt;/code> VIP range (&lt;code>199.36.153.4/30&lt;/code>) and a VPC route sending that /30 via the default internet gateway. After that, the traffic stays on Google&amp;rsquo;s backbone and skips the NAT gateway.&lt;/p></description></item></channel></rss>