<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on</title><link>https://www.alexander-koepke.de/categories/kubernetes/</link><description>Recent content in Kubernetes on</description><generator>Hugo</generator><language>de-de</language><lastBuildDate>Mon, 10 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.alexander-koepke.de/categories/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Diagnosing Distroless .NET Applications on Kubernetes</title><link>https://www.alexander-koepke.de/post/2026-08-10_dotnet-k8s-debug-containers/</link><pubDate>Mon, 10 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.alexander-koepke.de/post/2026-08-10_dotnet-k8s-debug-containers/</guid><description>&lt;h1 id="diagnosing-distroless-net-applications-on-kubernetes"&gt;Diagnosing Distroless .NET Applications on Kubernetes&lt;/h1&gt;
&lt;p&gt;Minimal container images are a good production default. Distroless and chiseled
.NET images reduce image size and attack surface by leaving out package managers,
shells, and troubleshooting tools.&lt;/p&gt;
&lt;p&gt;That becomes a challenge when a running application has high CPU usage, increasing
memory consumption, or unexplained latency. Installing tools in the application
container is not an option, and rebuilding the image changes the environment that
needs to be investigated.&lt;/p&gt;</description></item></channel></rss>