
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s tech blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, distributed training, and data engineering.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Sun, 14 Jun 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/udp/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/kubernetes/2026-06-14-ingress-tcp-udp-services.en</guid>
    <title>Exposing TCP/UDP Services with Ingress — The Limits of L4 and How to Work Around Them</title>
    <link>https://www.youngju.dev/blog/kubernetes/2026-06-14-ingress-tcp-udp-services.en</link>
    <description>Ingress is fundamentally an L7 (HTTP) abstraction. Yet when you must expose TCP/UDP services like databases, game servers, or DNS, this post shows how to use the ingress-nginx ConfigMap, Traefik EntryPoints, TLS passthrough, and the Gateway API TCPRoute/UDPRoute, and offers criteria for choosing dedicated L4 solutions instead.</description>
    <pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ingress</category><category>kubernetes</category><category>tcp</category><category>udp</category><category>networking</category><category>devops</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/kubernetes/2026-06-14-ingress-tcp-udp-services.ja</guid>
    <title>Ingress で TCP/UDP サービスを公開する — L4 の限界と解法</title>
    <link>https://www.youngju.dev/blog/kubernetes/2026-06-14-ingress-tcp-udp-services.ja</link>
    <description>Ingress は本来 L7（HTTP）の抽象です。それでもデータベース、ゲームサーバー、DNS のような TCP/UDP サービスを公開する必要があるとき、ingress-nginx の ConfigMap、Traefik の EntryPoint、TLS passthrough、Gateway API の TCPRoute/UDPRoute をどう使うかを整理し、専用 L4 ソリューションとの選択基準を示します。</description>
    <pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ingress</category><category>kubernetes</category><category>tcp</category><category>udp</category><category>networking</category><category>devops</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/kubernetes/2026-06-14-ingress-tcp-udp-services</guid>
    <title>Ingress로 TCP/UDP 서비스 노출하기 — L4의 한계와 해법</title>
    <link>https://www.youngju.dev/blog/kubernetes/2026-06-14-ingress-tcp-udp-services</link>
    <description>Ingress는 본래 L7(HTTP) 추상화입니다. 그럼에도 데이터베이스, 게임 서버, DNS 같은 TCP/UDP 서비스를 노출해야 할 때 ingress-nginx ConfigMap, Traefik EntryPoint, TLS passthrough, Gateway API의 TCPRoute/UDPRoute를 어떻게 쓰는지 정리하고 전용 L4 솔루션과의 선택 기준을 제시합니다.</description>
    <pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ingress</category><category>kubernetes</category><category>tcp</category><category>udp</category><category>networking</category><category>devops</category>
  </item>

    </channel>
  </rss>
