<?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>routing on Dileep Kumar</title>
    <link>https://dileepkumar.dev/tags/routing/</link>
    <description>Recent content in routing on Dileep Kumar</description>
    <image>
      <title>Dileep Kumar</title>
      <url>https://dileepkumar.dev/papermod-cover.png</url>
      <link>https://dileepkumar.dev/papermod-cover.png</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 13 Jan 2025 00:15:00 +0530</lastBuildDate><atom:link href="https://dileepkumar.dev/tags/routing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes Ingress: Advanced HTTP Routing and Load Balancing</title>
      <link>https://dileepkumar.dev/post/kubernetes-ingress-guide/</link>
      <pubDate>Mon, 13 Jan 2025 00:15:00 +0530</pubDate>
      
      <guid>https://dileepkumar.dev/post/kubernetes-ingress-guide/</guid>
      <description>Introduction Exposing multiple services with LoadBalancer creates multiple cloud load balancers (expensive!). Ingress provides HTTP/HTTPS routing to multiple services using a single load balancer, with features like path-based routing, SSL termination, and virtual hosting.
Understanding Kubernetes Ingress The Problem Without Ingress:
Service 1 → LoadBalancer ($$$) Service 2 → LoadBalancer ($$$) Service 3 → LoadBalancer ($$$) Total: 3 load balancers, high cost! The Solution With Ingress:
┌─→ Service 1 Ingress Controller ─┼─→ Service 2 (Single LB) └─→ Service 3 Total: 1 load balancer, low cost!</description>
    </item>
    
  </channel>
</rss>
