
  <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 blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, and data engineering — plus mindset essays on confidence, routines, health, and sport psychology.</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/multitenancy/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/kubernetes/2026-06-14-ingress-controller-cost-multitenancy.en</guid>
    <title>Ingress Multitenancy and Cost Optimization — A Platform Teams Choice</title>
    <link>https://www.youngju.dev/blog/kubernetes/2026-06-14-ingress-controller-cost-multitenancy.en</link>
    <description>The trade-offs of a shared controller vs per-tenant controllers, namespace isolation, load balancer cost, resource quotas, noisy-neighbor prevention, security boundaries, and showback models — multi-tenant Ingress operations and cost optimization from a platform teams perspective.</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>networking</category><category>multitenancy</category><category>devops</category><category>cost-optimization</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/kubernetes/2026-06-14-ingress-controller-cost-multitenancy.ja</guid>
    <title>Ingress マルチテナンシーとコスト最適化 — プラットフォームチームの選択</title>
    <link>https://www.youngju.dev/blog/kubernetes/2026-06-14-ingress-controller-cost-multitenancy.ja</link>
    <description>共有コントローラ vs テナント別コントローラのトレードオフ、ネームスペース分離、ロードバランサコスト、リソースクォータ、ノイジーネイバー対策、セキュリティ境界、ショーバックモデルまで、マルチテナントIngress運用とコスト最適化をプラットフォームチームの観点で整理します。</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>networking</category><category>multitenancy</category><category>devops</category><category>cost-optimization</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/kubernetes/2026-06-14-ingress-controller-cost-multitenancy</guid>
    <title>Ingress 멀티테넌시와 비용 최적화 — 플랫폼 팀의 선택</title>
    <link>https://www.youngju.dev/blog/kubernetes/2026-06-14-ingress-controller-cost-multitenancy</link>
    <description>공유 컨트롤러 vs 테넌트별 컨트롤러의 트레이드오프, 네임스페이스 격리, 로드밸런서 비용, 리소스 쿼터, 시끄러운 이웃 방지, 보안 경계, 쇼백 모델까지 멀티테넌트 Ingress 운영과 비용 최적화를 플랫폼 팀 관점에서 정리합니다.</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>networking</category><category>multitenancy</category><category>devops</category><category>cost-optimization</category>
  </item>

    </channel>
  </rss>
