<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kyaml on Chetan&#39;s Portfolio</title>
    <link>https://chetan-thapliyal.cloud/tags/kyaml/</link>
    <description>Recent content in Kyaml 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/kyaml/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>
    
  </channel>
</rss>
