<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Snapshots on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/snapshots/</link>
    <description>Recent content in Snapshots on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 11 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/snapshots/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Kubernetes CSI Snapshot Management: External-Snapshotter vs Stash vs Velero</title>
      <link>https://www.pistack.xyz/posts/2026-05-11-kubernetes-csi-snapshot-management-external-snapshotter-stash-velero-guide/</link>
      <pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-11-kubernetes-csi-snapshot-management-external-snapshotter-stash-velero-guide/</guid>
      <description>&lt;p&gt;Kubernetes persistent volumes hold critical application data, and protecting that data requires reliable snapshot capabilities with proper lifecycle management and automated retention policies. The Container Storage Interface (CSI) introduced a standardized way to create volume snapshots, but managing those snapshots at scale demands dedicated tooling. This guide compares three approaches to Kubernetes CSI snapshot management: the official CSI external-snapshotter, AppsCode Stash, and VMware Tanzu Velero.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
