<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on Dev &amp; Platform Engineering Hub</title><link>https://rhidayat.work/topics/networking/</link><description>Recent content in Networking on Dev &amp; Platform Engineering Hub</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Rachmat Hidayat</copyright><lastBuildDate>Mon, 10 Aug 2026 00:30:00 +0000</lastBuildDate><atom:link href="https://rhidayat.work/topics/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes Ep 6: Ingress Controllers &amp; HTTP Path Routing</title><link>https://rhidayat.work/series/kubernetes/06-ingress-controllers-and-routing/</link><pubDate>Mon, 10 Aug 2026 00:30:00 +0000</pubDate><guid>https://rhidayat.work/series/kubernetes/06-ingress-controllers-and-routing/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;
 While L4 Kubernetes Services handle IP and port-level load balancing, modern web applications require Layer 7 HTTP/HTTPS routing features: URL path matching (&lt;code&gt;/api&lt;/code&gt; vs &lt;code&gt;/app&lt;/code&gt;), hostname routing (&lt;code&gt;api.example.com&lt;/code&gt;), SSL/TLS termination, and header rewriting. This is handled by &lt;strong&gt;Ingress&lt;/strong&gt;.
&lt;/div&gt;</description></item><item><title>Kubernetes Ep 5: Networking Services (ClusterIP, NodePort, LoadBalancer)</title><link>https://rhidayat.work/series/kubernetes/05-services-clusterip-nodeport-loadbalancer/</link><pubDate>Mon, 10 Aug 2026 00:25:00 +0000</pubDate><guid>https://rhidayat.work/series/kubernetes/05-services-clusterip-nodeport-loadbalancer/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;
 Pods are ephemeral—they are created, destroyed, and rescheduled dynamically, causing their IP addresses to change constantly. A &lt;strong&gt;Kubernetes Service&lt;/strong&gt; provides a stable, persistent virtual IP (VIP), DNS name, and load balancing frontend across a dynamic set of backend Pods.
&lt;/div&gt;</description></item><item><title>Docker Ep 3: Docker Networking Deep Dive</title><link>https://rhidayat.work/series/docker/03-docker-networking-deep-dive/</link><pubDate>Sun, 09 Aug 2026 16:30:00 +0000</pubDate><guid>https://rhidayat.work/series/docker/03-docker-networking-deep-dive/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;
 How do two containers on the same host talk to each other without exposing ports to the public internet? Docker uses Linux virtual network interfaces (&lt;code&gt;veth&lt;/code&gt; pairs) connected to a software &lt;code&gt;bridge&lt;/code&gt;.
&lt;/div&gt;</description></item><item><title>CKAD Ep 4: Services, Ingress &amp; Network Policies</title><link>https://rhidayat.work/series/kubernetes-certification-path/ckad/04-ckad-application-services-and-networking/</link><pubDate>Sun, 09 Aug 2026 14:15:00 +0000</pubDate><guid>https://rhidayat.work/series/kubernetes-certification-path/ckad/04-ckad-application-services-and-networking/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;
 Services provide stable IP addresses for ephemeral Pods, Ingress controllers route HTTP/S domain traffic at Layer 7, and NetworkPolicies act as Pod-level firewalls. In this episode, we build production manifests for all three.
&lt;/div&gt;</description></item></channel></rss>