<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Networkpolicy on Chetan&#39;s Portfolio</title>
    <link>https://chetan-thapliyal.cloud/tags/networkpolicy/</link>
    <description>Recent content in Networkpolicy on Chetan&#39;s Portfolio</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Chetan Thapliyal</copyright>
    <lastBuildDate>Sun, 22 Nov 2026 19:32:00 +0530</lastBuildDate><atom:link href="https://chetan-thapliyal.cloud/tags/networkpolicy/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>One Dash Between Isolated and Exposed: The AND/OR Trap in Kubernetes NetworkPolicy</title>
      <link>https://chetan-thapliyal.cloud/posts/kubernetes-networkpolicy-and-or-yaml-kyaml/</link>
      <pubDate>Sun, 22 Nov 2026 19:32:00 +0530</pubDate>
      
      <guid>https://chetan-thapliyal.cloud/posts/kubernetes-networkpolicy-and-or-yaml-kyaml/</guid>
      <description>In a NetworkPolicy, whether two selectors mean AND or OR comes down to a single dash in the YAML. One version lets only a database&amp;rsquo;s exporter in; the other lets in a whole namespace, or every pod in the cluster. The API server accepts both without a word. Why that happens, how to see it, and why KYAML makes it visible.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/kubernetes-networkpolicy-and-or-yaml-kyaml/featured.png" />
        <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/kubernetes-networkpolicy-and-or-yaml-kyaml/featured.png" />
    </item>
    
    <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>
    
    <item>
      <title>From Docker Compose to Kubernetes: Moving My First Apps, Platform First</title>
      <link>https://chetan-thapliyal.cloud/posts/docker-compose-to-kubernetes-first-apps/</link>
      <pubDate>Thu, 19 Nov 2026 10:18:46 +0530</pubDate>
      
      <guid>https://chetan-thapliyal.cloud/posts/docker-compose-to-kubernetes-first-apps/</guid>
      <description>Three self-hosted apps moved from Docker Compose on a cloud VM to my K3s cluster in one day. The platform they needed first, the guardrails every app inherits, how each Compose line became a Kubernetes object, what a read-only root filesystem broke, and the row counts that proved each move.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/docker-compose-to-kubernetes-first-apps/featured.png" />
        <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://chetan-thapliyal.cloud/posts/docker-compose-to-kubernetes-first-apps/featured.png" />
    </item>
    
  </channel>
</rss>
