Provision and Configure a PersistentVolume and PersistentVolumeClaim for a Deployment

A PersistentVolume is a cluster-scoped resource — it does not belong to a namespace. Create the file and apply it:

kubectl apply -f pv.yaml
kubectl get pv jupiter-project-jupiter-pv

Expected status: Available

The key fields to get right:

spec:
  capacity:
    storage: ___
  accessModes:
    - ___
  hostPath:
    path: ___
  storageClassName: ""

Setting storageClassName: "" is required for static provisioning. Without it, Kubernetes may attempt dynamic provisioning and the PVC will never bind to this PV.

Documentation

• Persistent Volumes

Create the PVC in the jupiter namespace:

kubectl apply -f pvc.yaml
kubectl get pvc -n jupiter
kubectl get pv jupiter-project-jupiter-pv

Expected: PVC status Bound, PV status Bound.

The key fields:

metadata:
  namespace: jupiter
spec:
  accessModes:
    - ___
  resources:
    requests:
      storage: ___
  storageClassName: ""
  volumeName: ___   # optional but recommended — pins the claim to the correct PV

If the PVC stays Pending, check that storageClassName, accessModes, and storage match the PV exactly.

Documentation

• Persistent Volumes — PersistentVolumeClaims

A Deployment references a PVC through a volume definition in the pod spec and a volumeMount in the container spec. Two separate fields must both be present:

spec:
  template:
    spec:
      containers:
      - name: ___
        image: ___
        volumeMounts:
        - name: ___
          mountPath: ___
      volumes:
      - name: ___
        persistentVolumeClaim:
          claimName: ___

Apply and verify:

kubectl apply -f deployment.yaml
kubectl get pods -n jupiter
kubectl describe pod <pod-name> -n jupiter | grep -A5 Volumes

Documentation

• Configure a Pod to Use a PersistentVolume for Storage