<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Containers - Tag - Personal Blog | Jan-Otto Kröpke</title><link>https://jkroepke.de/tags/containers/</link><description>Containers - Tag - Personal Blog | Jan-Otto Kröpke</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>mail@jkroepke.de (Jan-Otto Kröpke)</managingEditor><webMaster>mail@jkroepke.de (Jan-Otto Kröpke)</webMaster><lastBuildDate>Thu, 23 Jul 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://jkroepke.de/tags/containers/" rel="self" type="application/rss+xml"/><item><title>Kubernetes Image Volumes for Platform-Managed Runtimes - Part 1</title><link>https://jkroepke.de/2026/07/kubernetes-image-volumes-for-platform-managed-runtimes-part-1/</link><pubDate>Thu, 23 Jul 2026 00:00:00 +0200</pubDate><author>mail@jkroepke.de (Jan-Otto Kröpke)</author><guid>https://jkroepke.de/2026/07/kubernetes-image-volumes-for-platform-managed-runtimes-part-1/</guid><description><![CDATA[<div class="featured-image">
                <img src="/images/plattform-managed-runtime.png" referrerpolicy="no-referrer">
            </div><p>Since Kubernetes v1.36, <a href="https://kubernetes.io/docs/tasks/configure-pod-container/image-volumes/" target="_blank" rel="noopener noreffer ">image volumes</a> are stable. They allow Kubernetes to pull an OCI image or artifact and mount its filesystem into a container. At first glance, this looks like a small storage feature, but it enables a much more interesting concept: <strong>platform-managed runtimes</strong>.</p>
<p>In this model, the application team publishes the application artifact, while the platform team provides and maintains the environment required to run it. Kubernetes combines both when the Pod starts, so the application team no longer needs to package Java, operating system libraries, and CA certificates into every application image.</p>]]></description></item></channel></rss>