<?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>Cilium on History</title><link>https://kukie.tech/tags/cilium/</link><description>Recent content in Cilium 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/cilium/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><item><title>Network &amp; K8s.04-2 A Name Becomes a Door</title><link>https://kukie.tech/posts/network-k8s-04-2/</link><pubDate>Wed, 28 Oct 2026 09:00:00 +0900</pubDate><guid>https://kukie.tech/posts/network-k8s-04-2/</guid><description>How a Pod reaches a Pod that keeps changing — a three-node kind lab with Cilium as a plain CNI, how a Service&amp;rsquo;s virtual IP is rewritten to a real Pod IP by node rules at PREROUTING and OUTPUT, why the iptables chain says 1/4·1/3·1/2 and spreads connections rather than requests, how db becomes db.cn4.svc.cluster.local and what CoreDNS does with it, where search and ndots multiply queries, and what dual-stack actually changes in Pod, Service and EndpointSlice fields.</description></item><item><title>Network &amp; K8s.04-1 One IP per Room</title><link>https://kukie.tech/posts/network-k8s-04-1/</link><pubDate>Mon, 26 Oct 2026 09:00:00 +0900</pubDate><guid>https://kukie.tech/posts/network-k8s-04-1/</guid><description>The Kubernetes network model read from the room up — why a Pod gets one IP and shares it across containers, the three rules every CNI must satisfy and where NAT still lives, how a Pod IP is born in two steps and dies only with the Pod, what kubelet actually does when it probes, and the /24-vs-/32 choice that decides whether the host sees every packet.</description></item><item><title>Kukie Infra.10 Hosting Cluster Isolation</title><link>https://kukie.tech/posts/kukie-infra-10/</link><pubDate>Thu, 22 Oct 2026 09:00:00 +0900</pubDate><guid>https://kukie.tech/posts/kukie-infra-10/</guid><description>Isolating other people&amp;rsquo;s code on a shared EKS hosting cluster — why gVisor over plain containers, Fargate or per-team nodes, why Cilium replaces the default VPC CNI while the cluster is still empty, how the node bootstrap installs a pinned and checksummed gVisor that fails closed, the missing gvisor-bin directory that broke the first apply, and the app domain and __Host- cookie that keep user apps away from the dashboard.</description></item></channel></rss>