<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pod-Security-Admission on Chetan&#39;s Portfolio</title>
    <link>https://chetan-thapliyal.cloud/tags/pod-security-admission/</link>
    <description>Recent content in Pod-Security-Admission on Chetan&#39;s Portfolio</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Chetan Thapliyal</copyright>
    <lastBuildDate>Fri, 20 Nov 2026 12:20:00 +0530</lastBuildDate><atom:link href="https://chetan-thapliyal.cloud/tags/pod-security-admission/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Pod Security, Honestly: Six Namespaces Restricted, Three That Can&#39;t Be</title>
      <link>https://chetan-thapliyal.cloud/posts/pod-security-honestly/</link>
      <pubDate>Fri, 20 Nov 2026 12:20:00 +0530</pubDate>
      
      <guid>https://chetan-thapliyal.cloud/posts/pod-security-honestly/</guid>
      <description>On the morning of 20 November one namespace in my homelab cluster enforced Pod Security restricted. By the evening six did, and the two namespaces in front of every app denied network traffic by default. What it cost (almost nothing, and why), the one subtle rule each policy needed, and the three namespaces that stay privileged on purpose.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/pod-security-honestly/featured.png" />
        <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/pod-security-honestly/featured.png" />
    </item>
    
  </channel>
</rss>
