<?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>Service Mesh on wid's blog</title><link>https://wid-blog.github.io/tags/service-mesh/</link><description>Recent content in Service Mesh on wid's blog</description><generator>Hugo</generator><language>ko</language><lastBuildDate>Wed, 10 Jul 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/tags/service-mesh/index.xml" rel="self" type="application/rss+xml"/><item><title>Envoy — 정적 reverse proxy가 cloud-native에서 마주친 한계</title><link>https://wid-blog.github.io/posts/tech/infra/envoy-and-l7-dynamic-proxy/</link><pubDate>Wed, 10 Jul 2024 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/posts/tech/infra/envoy-and-l7-dynamic-proxy/</guid><description>수동 reload, 정적 upstream, 빈약한 L7 observability — 정적 reverse proxy가 cloud-native 환경에서 마주친 한계를 Envoy의 xDS와 filter chain이 어떻게 푸는지 정리한다.</description></item></channel></rss>