Menu

Day 10: Persistent Volumes (PV/PVC) — Managing Heavy Model Weights and Vector Stores
📰

Day 10: Persistent Volumes (PV/PVC) — Managing Heavy Model Weights and Vector Stores

DEV Community: kubernetes·Suresh Kumar Pallapothu·about 1 hour ago
#dXcQy77o
#devtokubernetes#devto#dev#pv#pvc
Reading 0:00
15s threshold

Pods are ephemeral . If every restart downloads a 10 to 30 GB model, you saturate bandwidth, slow every rolling update and can face 10 to 15 minute cold starts. The fix is to keep the weights on storage that outlives the pod.

Diagram: FIG 1 · Downloading a large model on each restart saturates bandwidth and slows rolling updates. A volume that already holds the weights turns minutes into seconds. See the animated version .

Three layers of storage

StorageClass: how storage is provisioned: a local path, AWS EBS, Ceph RBD and so on.

PersistentVolume (PV): a piece of storage provisioned by an administrator or dynamically.

PersistentVolumeClaim (PVC): the developer's request. It binds to a matching PV, and pods reference the claim.

Diagram: FIG 2 · A StorageClass describes how storage is provisioned, a PersistentVolume is the storage itself and a PersistentVolumeClaim is the request that pods reference. See the animated version .

Access modes

ReadWriteOnce (RWO): read-write on a single node.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.