0Pricing
Docker & Kubernetes for Developers · Lección

Persistent Volumes y Persistent Volume Claims

Comprenda cómo aprovisionar y consumir almacenamiento dinámicamente en Kubernetes mediante PV y PVC.

Persistent Volumes y Persistent Volume Claims es una lección gratuita de Docker & Kubernetes for Developers en CoddyKit. Esta es la lección 1 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Docker & Kubernetes for Developers, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Docker & Kubernetes for Developers incluye 4 lecciones en total.

Partes de esta lección aún no han sido traducidas y se muestran en inglés.

Ephemeral Pods, Persistent Data

In Kubernetes, Pods are designed to be temporary and replaceable. If a Pod crashes or is rescheduled, any data stored directly within it is lost.

This ephemeral nature is great for stateless applications, but what about applications that need to store data persistently, like databases or file servers?

Introducing Persistent Volumes

A Persistent Volume (PV) is a piece of storage in the cluster that has been provisioned by an administrator or dynamically by Kubernetes.

It's an abstraction of the underlying storage (like a cloud disk, NFS share, or local disk), making it available for use by Pods without them needing to know the storage's specifics.

PV Capacity & Access Modes

Each PV has specific characteristics:

  • Capacity: The size of the storage, e.g., 10Gi.
  • Access Modes: How the storage can be mounted by Pods.
  • Reclaim Policy: What happens to the volume after a Pod is done using it.

These properties help Kubernetes match storage requests to available volumes.

How Pods Access Storage

PV Access Modes define how the volume can be mounted:

  • ReadWriteOnce (RWO): The volume can be mounted as read-write by a single node.
  • ReadOnlyMany (ROX): The volume can be mounted as read-only by many nodes.
  • ReadWriteMany (RWX): The volume can be mounted as read-write by many nodes.

Not all storage types support all modes. For example, a local disk typically only supports RWO.

Handling Released PVs

A PV's Reclaim Policy dictates what happens to the underlying storage when the PV is released from its claim:

  • Retain: Manual reclamation. Data remains, administrator must manually delete.
  • Delete: The underlying storage is automatically deleted along with the PV. This is common for dynamically provisioned volumes.
  • Recycle: (Deprecated) Wipes the volume and makes it available again.

Retain is useful for critical data that needs manual review before deletion.

Requesting Persistent Storage

A Persistent Volume Claim (PVC) is a request for storage by a user or application.

Think of it like a request for a specific type and size of storage. Instead of directly interacting with PVs, Pods request storage through PVCs.

PVCs provide a layer of abstraction, allowing developers to request storage without knowing the underlying infrastructure details.

Matching Storage Requests

When a PVC is created, Kubernetes tries to find a suitable PV to bind it to. This process is called binding.

It looks for PVs that meet the PVC's requirements:

  • Capacity (size)
  • Access Modes
  • Storage Class (if specified)

Once bound, the PV is exclusively reserved for that PVC.

Defining a Basic PV

Here's how you might define a simple hostPath Persistent Volume. This type uses a directory on the node's filesystem, primarily for single-node testing.

Try running this example (kubectl apply -f pv.yaml):

apiVersion: v1
kind: PersistentVolume
metadata:
  name: my-pv
spec:
  capacity:
    storage: 1Gi
  volumeMode: Filesystem
  accessModes:
    - ReadWriteOnce
  persistentVolumeReclaimPolicy: Retain
  hostPath:
    path: "/mnt/data"

Requesting Storage with a PVC

Now, let's create a Persistent Volume Claim that requests 1Gi of storage with ReadWriteOnce access. It will bind to our my-pv if available.

Try running this example (kubectl apply -f pvc.yaml):

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: my-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi

Attaching PVC to a Pod

Finally, let's see how a Pod can use the storage provided by our PVC. We reference the PVC in the Pod's volumes section and then mount it into a container.

Try running this example (kubectl apply -f pod.yaml):

apiVersion: v1
kind: Pod
metadata:
  name: my-app-pod
spec:
  volumes:
    - name: my-storage
      persistentVolumeClaim:
        claimName: my-pvc
  containers:
    - name: my-container
      image: busybox
      command: ["sh", "-c", "echo 'Hello from CoddyKit!' > /data/message.txt && sleep 3600"]
      volumeMounts:
        - mountPath: "/data"
          name: my-storage

PV vs. PVC Roles

Understanding the distinct roles of Persistent Volumes (PVs) and Persistent Volume Claims (PVCs) is crucial for managing storage in Kubernetes.

Which statement accurately describes the primary role of a Persistent Volume (PV)?

Recap: Persistent Storage

Great job! You've learned how Kubernetes manages persistent storage:

  • Persistent Volumes (PVs) abstract physical storage resources.
  • Persistent Volume Claims (PVCs) are user requests for storage.
  • PVs have capacity, access modes (RWO, ROX, RWX), and reclaim policies (Retain, Delete).
  • PVCs bind to available PVs, and Pods then use PVCs to mount storage.

This system allows applications to reliably store data, even when Pods are recreated or moved.

Preguntas frecuentes

¿La lección «Persistent Volumes y Persistent Volume Claims» es gratis?

Sí — el texto completo de «Persistent Volumes y Persistent Volume Claims» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Docker & Kubernetes for Developers, actualiza a CoddyKit PRO. El curso de Docker & Kubernetes for Developers incluye 4 lecciones en total.

¿Qué aprenderé en «Persistent Volumes y Persistent Volume Claims»?

Comprenda cómo aprovisionar y consumir almacenamiento dinámicamente en Kubernetes mediante PV y PVC. Practicas Docker & Kubernetes for Developers con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.

¿Necesito experiencia previa para empezar Docker & Kubernetes for Developers?

No se requiere experiencia previa. Docker & Kubernetes for Developers en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 1 de 4.

¿Cuánto tiempo toma la lección «Persistent Volumes y Persistent Volume Claims»?

La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.

¿Puedo escribir y ejecutar código en esta lección de Docker & Kubernetes for Developers?

Sí. Cada lección de Docker & Kubernetes for Developers incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.

Todas las lecciones de este curso

  1. Persistent Volumes y Persistent Volume Claims
  2. Gestión de aplicaciones con estado mediante StatefulSets
  3. ConfigMaps y Secrets para la configuración
  4. Clases de almacenamiento y aprovisionamiento dinámico
← Volver a Docker & Kubernetes for Developers