<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GitOps on Ivan Versluis — Networknet</title><link>https://networknet.nl/tags/gitops/</link><description>Recent content in GitOps on Ivan Versluis — Networknet</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 06 Sep 2026 10:45:43 +0200</lastBuildDate><atom:link href="https://networknet.nl/tags/gitops/index.xml" rel="self" type="application/rss+xml"/><item><title>Learning the network by denying it first</title><link>https://networknet.nl/notes/zero-trust-network-policies/</link><pubDate>Sun, 06 Sep 2026 10:00:00 +0200</pubDate><guid>https://networknet.nl/notes/zero-trust-network-policies/</guid><description>&lt;h2 id="segmentation-as-a-learning-method">Segmentation as a learning method&lt;/h2>
&lt;p>Kubernetes makes it easy for workloads to communicate. That convenience also means a compromised workload may reach more services than its use case requires. I wanted my homelab namespaces to start from the opposite assumption: traffic is denied until a workload has an understood reason to send or receive it.&lt;/p>
&lt;p>This turns Zero Trust into an engineering practice. Each use case gets its own explicit network boundaries, and implementing those boundaries forces me to learn the real data flow rather than relying on an architecture diagram alone.&lt;/p></description></item></channel></rss>