<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sidecarless on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/sidecarless/</link>
    <description>Recent content in Sidecarless on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/sidecarless/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Sidecarless Service Mesh Architecture: Istio Ambient vs Cilium vs Linkerd (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-20-self-hosted-sidecarless-service-mesh-istio-ambient-cilium-linkerd-guide/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-20-self-hosted-sidecarless-service-mesh-istio-ambient-cilium-linkerd-guide/</guid>
      <description>&lt;p&gt;Traditional service mesh architectures rely on sidecar proxies — additional containers injected alongside each application pod to intercept and manage network traffic. While effective, this approach introduces resource overhead, operational complexity, and performance penalties from double network hops. In 2026, a new paradigm has emerged: &lt;strong&gt;sidecarless service mesh architecture&lt;/strong&gt;, which eliminates per-pod sidecars by handling traffic management at the node or kernel level.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
