<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Service Mesh Field Report (English)</title>
    <link>https://www.service-mesh-field-report.de/en</link>
    <atom:link href="https://www.service-mesh-field-report.de/en/rss.xml" rel="self" type="application/rss+xml" />
    <description>The complete archive of the Service Mesh Field Report series: weekly field notes from running Istio and Envoy in the enterprise. Real incidents, the patterns behind them, and what they mean for decision makers.</description>
    <language>en-GB</language>
    <item>
      <title>Service Mesh Field Report #12 - Four Questions, and You Can Read Any Envoy Mesh</title>
      <link>https://www.service-mesh-field-report.de/en/12-four-questions-read-any-envoy-mesh</link>
      <guid isPermaLink="true">https://www.service-mesh-field-report.de/en/12-four-questions-read-any-envoy-mesh</guid>
      <pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate>
      <description>Almost every mesh runs the same engine. Today I take it apart. Don't fear the depth, there are exactly four parts.</description>
    </item>
    <item>
      <title>Service Mesh Field Report #11 - Almost Every Mesh Runs the Same Engine</title>
      <link>https://www.service-mesh-field-report.de/en/11-almost-every-mesh-runs-the-same-engine</link>
      <guid isPermaLink="true">https://www.service-mesh-field-report.de/en/11-almost-every-mesh-runs-the-same-engine</guid>
      <pubDate>Thu, 09 Jul 2026 00:00:00 GMT</pubDate>
      <description>Istio, Kuma, Consul, App Mesh, Gloo. Five names, and under the hood the same proxy five times: Envoy.</description>
    </item>
    <item>
      <title>Service Mesh Field Report #10 - The Real Problem Was Never Istio</title>
      <link>https://www.service-mesh-field-report.de/en/10-real-problem-was-never-istio</link>
      <guid isPermaLink="true">https://www.service-mesh-field-report.de/en/10-real-problem-was-never-istio</guid>
      <pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate>
      <description>Ten Field Reports. Almost all of them had the same root cause. And it was never in Istio.</description>
    </item>
    <item>
      <title>Service Mesh Field Report #9 - Observability that actually helps in an incident</title>
      <link>https://www.service-mesh-field-report.de/en/09-observability-that-helps-in-incidents</link>
      <guid isPermaLink="true">https://www.service-mesh-field-report.de/en/09-observability-that-helps-in-incidents</guid>
      <pubDate>Thu, 25 Jun 2026 00:00:00 GMT</pubDate>
      <description>During an incident, most people open Grafana first. Everything green. That's exactly where the team gets stuck.</description>
    </item>
    <item>
      <title>Service Mesh Field Report #8 - The Diagnostic Path Every Team Gets</title>
      <link>https://www.service-mesh-field-report.de/en/08-diagnostic-path-every-team-gets</link>
      <guid isPermaLink="true">https://www.service-mesh-field-report.de/en/08-diagnostic-path-every-team-gets</guid>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>Two teams last week: one guesses for three hours, one is done in twenty minutes. The difference isn't talent. It's this one path.</description>
    </item>
    <item>
      <title>Service Mesh Field Report #7 - The scariest error message usually has the most mundane cause</title>
      <link>https://www.service-mesh-field-report.de/en/07-scariest-error-message-mundane-cause</link>
      <guid isPermaLink="true">https://www.service-mesh-field-report.de/en/07-scariest-error-message-mundane-cause</guid>
      <pubDate>Thu, 11 Jun 2026 00:00:00 GMT</pubDate>
      <description>Most mesh incidents aren't hard. They just look that way.</description>
    </item>
    <item>
      <title>Service Mesh Field Report #6 - Allow locally, prevent mesh-wide</title>
      <link>https://www.service-mesh-field-report.de/en/06-allow-locally-prevent-mesh-wide</link>
      <guid isPermaLink="true">https://www.service-mesh-field-report.de/en/06-allow-locally-prevent-mesh-wide</guid>
      <pubDate>Thu, 04 Jun 2026 00:00:00 GMT</pubDate>
      <description>Closing the gap without taking away tenant autonomy.</description>
    </item>
    <item>
      <title>Service Mesh Field Report #5 - When One Tenant Hijacks Everyone Else's Traffic</title>
      <link>https://www.service-mesh-field-report.de/en/05-tenant-hijacks-mesh-traffic</link>
      <guid isPermaLink="true">https://www.service-mesh-field-report.de/en/05-tenant-hijacks-mesh-traffic</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Letting tenants create their own VirtualServices opens a door to MITM inside your own mesh.</description>
    </item>
    <item>
      <title>Service Mesh Field Report #4 - Whoever Owns the Mesh Decides What Stays</title>
      <link>https://www.service-mesh-field-report.de/en/04-who-owns-the-mesh-decides-what-stays</link>
      <guid isPermaLink="true">https://www.service-mesh-field-report.de/en/04-who-owns-the-mesh-decides-what-stays</guid>
      <pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate>
      <description>From Soltau, live at CloudLand: who's actually responsible in the mesh?</description>
    </item>
    <item>
      <title>Service Mesh Field Report #3 - What Nobody Understands Anymore, but Everyone Still Uses</title>
      <link>https://www.service-mesh-field-report.de/en/03-config-nobody-understands-everyone-uses</link>
      <guid isPermaLink="true">https://www.service-mesh-field-report.de/en/03-config-nobody-understands-everyone-uses</guid>
      <pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate>
      <description>20, 100, 500+ configuration objects - and no one dares to delete a thing.</description>
    </item>
    <item>
      <title>Service Mesh Field Report #2 - When the CVE Lands, It's Too Late</title>
      <link>https://www.service-mesh-field-report.de/en/02-cve-lands-too-late</link>
      <guid isPermaLink="true">https://www.service-mesh-field-report.de/en/02-cve-lands-too-late</guid>
      <pubDate>Thu, 07 May 2026 00:00:00 GMT</pubDate>
      <description>Istio ships a minor release every three months. Sounds predictable.</description>
    </item>
    <item>
      <title>Service Mesh Field Report #1 - When &quot;Secure&quot; Is Just a Gut Feeling</title>
      <link>https://www.service-mesh-field-report.de/en/01-secure-gut-feeling</link>
      <guid isPermaLink="true">https://www.service-mesh-field-report.de/en/01-secure-gut-feeling</guid>
      <pubDate>Thu, 30 Apr 2026 00:00:00 GMT</pubDate>
      <description>mTLS enabled everywhere, dashboards green - and nobody can say what actually runs encrypted.</description>
    </item>
  </channel>
</rss>
