<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>concept on Jaaved Ali Khan</title><link>https://jaaved.netlify.app/tags/concept/</link><description>Recent content in concept on Jaaved Ali Khan</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 14 Jan 2023 20:14:06 +0400</lastBuildDate><atom:link href="https://jaaved.netlify.app/tags/concept/index.xml" rel="self" type="application/rss+xml"/><item><title>Storage Classes</title><link>https://jaaved.netlify.app/notes/20210729180042-storage_classes/</link><pubDate>Sat, 14 Jan 2023 20:14:06 +0400</pubDate><guid>https://jaaved.netlify.app/notes/20210729180042-storage_classes/</guid><description>Tags # Summary # ref Different classes might map to quality-of-service levels, or to backup policies, or to arbitrary policies determined by the cluster administrators.
Each StorageClass contains the fields provisioner, parameters, and reclaimPolicy, which are used when a PersistentVolume belonging to the class needs to be dynamically provisioned.
*The name of a StorageClass object is significant, and is how users can request a particular class. Administrators set the name and other parameters of a class when first creating StorageClass objects, and the objects cannot be updated once they are created.</description></item></channel></rss>