<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>karpenter on Code it Yourself</title><link>https://carlos.mendible.com/tags/karpenter/</link><description>Recent content in karpenter on Code it Yourself</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Carlos Mendible</copyright><lastBuildDate>Mon, 11 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://carlos.mendible.com/tags/karpenter/index.xml" rel="self" type="application/rss+xml"/><item><title>AKS NAP: ZRS Disk PV Zone Fix with a Mutating Admission Webhook</title><link>https://carlos.mendible.com/2026/05/11/aks-nap-zrs-disk-pv-zone-fix-with-a-mutating-admission-webhook/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://carlos.mendible.com/2026/05/11/aks-nap-zrs-disk-pv-zone-fix-with-a-mutating-admission-webhook/</guid><description>&lt;p>If you are running AKS with Node Auto Provisioning (NAP/Karpenter) and using Azure Disk ZRS (Zone-Redundant Storage) Persistent Volumes with &lt;code>volumeBindingMode: Immediate&lt;/code>, you may have noticed that pods get stuck in &lt;code>Pending&lt;/code> state. In this post, I&amp;rsquo;ll show you a &lt;strong>temporary workaround&lt;/strong> using a Kubernetes mutating admission webhook that fixes this scheduling issue.&lt;/p></description></item></channel></rss>