<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mesh-Management on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/mesh-management/</link>
    <description>Recent content in Mesh-Management on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 21 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/mesh-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Service Mesh Management: Meshery vs Istioctl vs Kiali (2026 Guide)</title>
      <link>https://www.pistack.xyz/posts/2026-05-21-self-hosted-service-mesh-management-meshery-istioctl-kiali-guide/</link>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-21-self-hosted-service-mesh-management-meshery-istioctl-kiali-guide/</guid>
      <description>&lt;p&gt;Service meshes have become essential infrastructure for Kubernetes clusters handling east-west traffic, mutual TLS, and observability. But deploying a service mesh is only half the challenge — managing it over time is where teams struggle. How do you upgrade the control plane, debug routing failures, visualize traffic flows, and enforce security policies across hundreds of microservices?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
