<?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>Namespace on History</title><link>https://kukie.tech/tags/namespace/</link><description>Recent content in Namespace on History</description><generator>Hugo</generator><language>ko-kr</language><lastBuildDate>Wed, 21 Oct 2026 09:00:00 +0900</lastBuildDate><atom:link href="https://kukie.tech/tags/namespace/index.xml" rel="self" type="application/rss+xml"/><item><title>Network &amp; K8s.03-1 A Process in a Room</title><link>https://kukie.tech/posts/network-k8s-03-1/</link><pubDate>Wed, 21 Oct 2026 09:00:00 +0900</pubDate><guid>https://kukie.tech/posts/network-k8s-03-1/</guid><description>What a container actually is on an Ubuntu VM — three problems that VMs and containers each solve, the runtime stack from dockerd and kubelet down to runC, why runC vanishes and containerd-shim stays as the parent, the six namespaces and one cgroup directory seen through /proc.</description></item><item><title>Network &amp; K8s.02-1 Before the Packet</title><link>https://kukie.tech/posts/network-k8s-02-1/</link><pubDate>Fri, 16 Oct 2026 09:00:00 +0900</pubDate><guid>https://kukie.tech/posts/network-k8s-02-1/</guid><description>Inside the Linux kernel on an Ubuntu VM — a Python server under strace, the same socket seen from ss and /proc, why FD 4 comes back four times, interfaces as doors and lo as a mirror, veth pairs and a bridge built by hand, network namespaces as rooms, and nsenter into a Docker container&amp;rsquo;s room.</description></item></channel></rss>