<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Services on TheBigHouse</title><link>https://thebighouse.nl/tags/services/</link><description>Recent content in Services on TheBigHouse</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 11 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thebighouse.nl/tags/services/index.xml" rel="self" type="application/rss+xml"/><item><title>One front door: Services and Ingress</title><link>https://thebighouse.nl/writing/k8s-02-services-and-ingress/</link><pubDate>Sun, 11 Oct 2026 00:00:00 +0000</pubDate><guid>https://thebighouse.nl/writing/k8s-02-services-and-ingress/</guid><description>&lt;p&gt;Your application needs an address that survives the Pod running it.&lt;/p&gt;&#10;&lt;p&gt;In chapter one, you put nginx in a Pod and visited it through &lt;code&gt;kubectl port-forward&lt;/code&gt;. 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.&lt;/p&gt;&#10;&lt;p&gt;A Service provides that door. Ingress routes browser traffic to it. You can add both to the Docker Desktop cluster you already created.&lt;/p&gt;</description></item></channel></rss>