<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>persistent-volumes on Dileep Kumar</title>
    <link>https://dileepkumar.dev/tags/persistent-volumes/</link>
    <description>Recent content in persistent-volumes on Dileep Kumar</description>
    <image>
      <title>Dileep Kumar</title>
      <url>https://dileepkumar.dev/papermod-cover.png</url>
      <link>https://dileepkumar.dev/papermod-cover.png</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 13 Jan 2025 00:00:00 +0530</lastBuildDate><atom:link href="https://dileepkumar.dev/tags/persistent-volumes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes Storage Mastery: Persistent Volumes, Claims, and StatefulSets</title>
      <link>https://dileepkumar.dev/post/kubernetes-storage-mastery/</link>
      <pubDate>Mon, 13 Jan 2025 00:00:00 +0530</pubDate>
      
      <guid>https://dileepkumar.dev/post/kubernetes-storage-mastery/</guid>
      <description>Introduction Containers are ephemeral by nature - when they restart, all data is lost. For stateful applications like databases, this is unacceptable. Kubernetes provides a robust storage abstraction through Persistent Volumes (PV), Persistent Volume Claims (PVC), and Storage Classes to solve this challenge.
In this guide, I&amp;rsquo;ll show you how to implement persistent storage in Kubernetes, from basic concepts to production-ready StatefulSets.
Understanding Kubernetes Storage The Problem:
# Without persistent storage - data lost on restart!</description>
    </item>
    
  </channel>
</rss>
