Flats, not houses: Namespaces

Tue, 13 Oct 2026 00:00:00 +0000

Namespaces let development and production have their own copies of an application in the same cluster.

In chapter two, you gave nginx a front door. Add a development copy and naming things gets awkward. You could call everything nginx-development, nginx-production, and so on. Kubernetes gives you another place to put that distinction: the namespace.

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.

One front door: Services and Ingress

Sun, 11 Oct 2026 00:00:00 +0000

Your application needs an address that survives the Pod running it.

In chapter one, you put nginx in a Pod and visited it through kubectl port-forward. That works for a quick look. For an application people need to reach, I want a front door that stays put when the tenant moves out.

A Service provides that door. Ingress routes browser traffic to it. You can add both to the Docker Desktop cluster you already created.

Ingress on TheBigHouse

Flats, not houses: Namespaces

One front door: Services and Ingress