<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Clustermesh on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/clustermesh/</link>
    <description>Recent content in Clustermesh on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/clustermesh/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Kubernetes Multi-Cluster Service Connectivity: Cilium ClusterMesh vs Istio Multi-Primary vs Linkerd Multicluster (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-16-self-hosted-kubernetes-multi-cluster-service-connectivity-cilium-clustermesh-istio-linkerd-guide/</link>
      <pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-16-self-hosted-kubernetes-multi-cluster-service-connectivity-cilium-clustermesh-istio-linkerd-guide/</guid>
      <description>&lt;p&gt;Running Kubernetes across multiple clusters is increasingly common — for disaster recovery, geographic distribution, or separating workloads by team or environment. But connecting services across cluster boundaries introduces networking complexity. This guide compares three approaches to multi-cluster service connectivity: &lt;strong&gt;Cilium ClusterMesh&lt;/strong&gt;, &lt;strong&gt;Istio Multi-Primary&lt;/strong&gt;, and &lt;strong&gt;Linkerd Multicluster&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
