<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>oras on Code it Yourself</title><link>https://carlos.mendible.com/tags/oras/</link><description>Recent content in oras on Code it Yourself</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Carlos Mendible</copyright><lastBuildDate>Thu, 04 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://carlos.mendible.com/tags/oras/index.xml" rel="self" type="application/rss+xml"/><item><title>AKS: Mount Versioned Content as OCI Image Volumes</title><link>https://carlos.mendible.com/2026/06/04/aks-mount-versioned-content-as-oci-image-volumes/</link><pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate><guid>https://carlos.mendible.com/2026/06/04/aks-mount-versioned-content-as-oci-image-volumes/</guid><description>&lt;p>Kubernetes 1.36 graduated &lt;strong>image volumes&lt;/strong> to stable. This feature lets the kubelet pull any OCI artifact from a registry and mount its filesystem directly into pods as a &lt;strong>read-only volume&lt;/strong> — no init containers, no &lt;code>emptyDir&lt;/code> copies, no custom CSI drivers. In this post I&amp;rsquo;ll walk through a complete example: packaging versioned project content as a scratch-based OCI image and serving it from a Go HTTP API running on AKS.&lt;/p></description></item></channel></rss>