<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ceph on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/ceph/</link>
    <description>Recent content in Ceph on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 15 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/ceph/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Ceph Cluster Deployment: Cephadm vs Rook vs Ceph-ansible (2026 Guide)</title>
      <link>https://www.pistack.xyz/posts/2026-05-15-self-hosted-ceph-deployment-cephadm-vs-rook-vs-ceph-ansible-guide/</link>
      <pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-15-self-hosted-ceph-deployment-cephadm-vs-rook-vs-ceph-ansible-guide/</guid>
      <description>&lt;p&gt;Ceph is the leading open-source software-defined storage platform, providing object, block, and file storage in a unified system. But deploying and managing a Ceph cluster requires choosing the right orchestration tool. This guide compares the three most popular Ceph deployment methods: &lt;strong&gt;Cephadm&lt;/strong&gt; (the official orchestrator), &lt;strong&gt;Rook&lt;/strong&gt; (the Kubernetes operator), and &lt;strong&gt;Ceph-ansible&lt;/strong&gt; (the legacy Ansible-based approach).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Kubernetes CSI Drivers: Ceph CSI vs Longhorn vs Kadalu (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-08-kubernetes-csi-drivers-ceph-csi-vs-longhorn-vs-kadalu-guide/</link>
      <pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-08-kubernetes-csi-drivers-ceph-csi-vs-longhorn-vs-kadalu-guide/</guid>
      <description>&lt;p&gt;The Container Storage Interface (CSI) is the standard that Kubernetes uses to manage persistent storage for stateful workloads. Rather than baking storage drivers directly into the kubelet code, CSI enables third-party storage providers to deploy their own plugins as separate containers — giving you the flexibility to mix and match storage backends on a per-namespace or per-volume basis.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
