<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on RLGeeX</title><link>https://www.rlgeex.com/tags/networking/</link><description>Recent content in Networking on RLGeeX</description><generator>Hugo</generator><language>en-us</language><copyright>RLGeeX © 2025 - Real-Life Geeks providing expert IT consulting</copyright><lastBuildDate>Thu, 19 Feb 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://www.rlgeex.com/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Make every GCP VPC network custom mode from the first apply</title><link>https://www.rlgeex.com/news/make-every-gcp-vpc-network-custom-mode-from-the-first-apply/</link><pubDate>Thu, 19 Feb 2026 09:00:00 -0500</pubDate><guid>https://www.rlgeex.com/news/make-every-gcp-vpc-network-custom-mode-from-the-first-apply/</guid><description>&lt;p>If you are a cloud engineer building a Google Cloud foundation in Terraform, the network is one of the first modules you write and one of the last you will want to change. My argument is that every VPC network in your foundation should be custom mode from the first apply, and new projects should not get a default network at all. This post covers why, which settings carry the decision, and where auto mode is still fine.&lt;/p></description></item></channel></rss>