<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Namespaces on TheBigHouse</title><link>https://thebighouse.nl/tags/namespaces/</link><description>Recent content in Namespaces on TheBigHouse</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 13 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thebighouse.nl/tags/namespaces/index.xml" rel="self" type="application/rss+xml"/><item><title>Flats, not houses: Namespaces</title><link>https://thebighouse.nl/writing/k8s-03-namespaces/</link><pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate><guid>https://thebighouse.nl/writing/k8s-03-namespaces/</guid><description>&lt;p&gt;Namespaces let development and production have their own copies of an application in the same cluster.&lt;/p&gt;&#10;&lt;p&gt;In chapter two, you gave nginx a front door. Add a development copy and naming things gets awkward. You could call everything &lt;code&gt;nginx-development&lt;/code&gt;, &lt;code&gt;nginx-production&lt;/code&gt;, and so on. Kubernetes gives you another place to put that distinction: the namespace.&lt;/p&gt;&#10;&lt;p&gt;Think of a cluster as a building with several flats. Each flat can have its own kitchen without the residents agreeing on a unique name for it. A namespace gives a group of Kubernetes resources that kind of address.&lt;/p&gt;</description></item></channel></rss>