<?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>Postgresql on History</title><link>https://kukie.tech/tags/postgresql/</link><description>Recent content in Postgresql on History</description><generator>Hugo</generator><language>ko-kr</language><lastBuildDate>Fri, 30 Oct 2026 09:00:00 +0900</lastBuildDate><atom:link href="https://kukie.tech/tags/postgresql/index.xml" rel="self" type="application/rss+xml"/><item><title>Network &amp; K8s.04-3 Who May Knock</title><link>https://kukie.tech/posts/network-k8s-04-3/</link><pubDate>Fri, 30 Oct 2026 09:00:00 +0900</pubDate><guid>https://kukie.tech/posts/network-k8s-04-3/</guid><description>Having a path is not the same as being allowed to use it — a three-Pod lab (diagnostic, Go web server, PostgreSQL) shows what a NetworkPolicy really is: a per-Pod, per-direction allow list where both the sender&amp;rsquo;s egress door and the receiver&amp;rsquo;s ingress door must open, allow rules only add up, an empty selector, an empty list and an empty rule mean three different things, a hyphen in YAML decides AND versus OR, and the standard API stops at the TCP port while Cilium&amp;rsquo;s Envoy can refuse a single HTTP path with a 403.</description></item></channel></rss>