<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Security on Tech Notes - A Developer's Journal</title><link>https://oypron.com/tags/security/</link><description>Recent content in Security on Tech Notes - A Developer's Journal</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 05 Nov 2025 09:00:00 +0000</lastBuildDate><atom:link href="https://oypron.com/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes NetworkPolicy: A Practical Guide to Default-Deny</title><link>https://oypron.com/posts/kubernetes-network-policies/</link><pubDate>Wed, 05 Nov 2025 09:00:00 +0000</pubDate><guid>https://oypron.com/posts/kubernetes-network-policies/</guid><description>&lt;p&gt;The first time I tried to enforce NetworkPolicy in a real cluster, I broke DNS for an entire namespace and spent the next forty minutes wondering why every pod was returning &lt;code&gt;i/o timeout&lt;/code&gt;. This post is the guide I wish I had read first.&lt;/p&gt;
&lt;h2 id="the-mental-model"&gt;The mental model&lt;/h2&gt;
&lt;p&gt;A NetworkPolicy is a label-selector-driven firewall rule. It only does two things:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Selects pods&lt;/strong&gt; by label (in a single namespace).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Specifies allowed ingress, egress, or both&lt;/strong&gt; for those pods.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Three rules that took me too long to internalize:&lt;/p&gt;</description></item></channel></rss>