<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Multi-Tenancy on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/multi-tenancy/</link>
    <description>Recent content in Multi-Tenancy on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 28 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/multi-tenancy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>vCluster vs Capsule vs Loft: Kubernetes Namespace &amp; Virtual Cluster Management 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-28-vcluster-vs-capsule-vs-loft-kubernetes-namespace-virtual-cluster-guide-2026/</link>
      <pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-28-vcluster-vs-capsule-vs-loft-kubernetes-namespace-virtual-cluster-guide-2026/</guid>
      <description>&lt;p&gt;Running multiple teams, environments, or workloads on a single Kubernetes cluster requires careful isolation. Standard Kubernetes namespaces provide basic segmentation, but they fall short when teams need their own control plane, custom resource definitions, or independent RBAC policies. This is where virtual cluster and namespace management solutions come in.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
