<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Namespace on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/namespace/</link>
    <description>Recent content in Namespace on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 12 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/namespace/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Kubernetes Namespace Lifecycle Management: Tools and Best Practices</title>
      <link>https://www.pistack.xyz/posts/2026-05-12-self-hosted-kubernetes-namespace-lifecycle-management/</link>
      <pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-12-self-hosted-kubernetes-namespace-lifecycle-management/</guid>
      <description>&lt;p&gt;Kubernetes namespaces provide logical isolation within a single cluster, enabling teams to organize workloads, apply resource quotas, and enforce access controls. In self-hosted clusters with multiple teams or projects, managing the full namespace lifecycle — creation, configuration, monitoring, and eventual deletion — becomes a critical operational concern. Without proper lifecycle management, namespaces accumulate stale resources, leak resource quotas, and become security liabilities.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
