<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secrets on TheBigHouse</title><link>https://thebighouse.nl/tags/secrets/</link><description>Recent content in Secrets on TheBigHouse</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 17 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thebighouse.nl/tags/secrets/index.xml" rel="self" type="application/rss+xml"/><item><title>Notes on the fridge: ConfigMaps and Secrets</title><link>https://thebighouse.nl/writing/k8s-05-configmaps-and-secrets/</link><pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate><guid>https://thebighouse.nl/writing/k8s-05-configmaps-and-secrets/</guid><description>&lt;p&gt;Give the same application different settings in development and production with ConfigMaps and Secrets.&lt;/p&gt;&#10;&lt;p&gt;Both flats now have nginx, but they still serve the same welcome page. A real application might need a different API address in development, or credentials for a production database. Baking those into the image would mean rebuilding it whenever a setting changes.&lt;/p&gt;&#10;&lt;p&gt;I prefer to keep the image the same and supply the settings separately. Think of a ConfigMap as a note on the fridge: instructions for whoever lives in that flat. Passwords deserve somewhere less public. Kubernetes has a separate resource for those, called a Secret, though the name needs a little unpacking.&lt;/p&gt;</description></item></channel></rss>