https://drive.google.com/file/d/13qUv3XlMUR9SMbpzN_DJOvpYroTldbZ_/view?usp=sharing

🔍 YAML Breakdown

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: myclaim
spec:
  accessModes:
    - ReadWriteMany
  volumeMode: Filesystem
  resources:
    requests:
      storage: 4Gi
  storageClassName: slow

🔑 Key Insight:

This PVC is a storage request that will bind to a compatible PV (like your pvone-nfs).

💡 How binding works:

Kubernetes matches PVC to PV based on:

• storageClassName (must match)
• accessModes (PVC modes ⊆ PV modes)
• storage (PV capacity ≥ PVC request)

📌 PVC-PV Binding Rules

✅ Result: PVC will bind to pvone-nfs → status = Bound

⚠️ Critical Note:

Your PV uses ReadWriteOnce, but NFS supports ReadWriteMany.

→ If your app needs shared access, change both PVC and PV to ReadWriteMany.

🧪 k3s Lab: Bind PVC to NFS PV

🔧 Step 1: Ensure PV Exists

💡 You should already have pvone-nfs from the previous lab:

kubectl get pv
# NAME        CAPACITY  ACCESS MODES  STATUS      CLAIM
# pvone-nfs   5Gi       RWO           Available   <none>

🔧 Step 2: Apply PVC

# Apply PVC
kubectl apply -f pvc-nfs.yaml

# Verify binding
kubectl get pvc
# NAME      STATUS   VOLUME       CAPACITY  ACCESS MODES
# myclaim   Bound    pvone-nfs    5Gi       RWO

kubectl get pv
# NAME        STATUS   CLAIM
# pvone-nfs   Bound    default/myclaim

🔍 Key Observation:

• PVC status = Bound
• PV is now claimed by default/myclaim

🔧 Step 3: Use PVC in a Pod

# pod-using-pvc.yaml
apiVersion: v1
kind: Pod
metadata:
  name: nfs-pod
spec:
  containers:
  - name: web
    image: nginx
    volumeMounts:
    - mountPath: /usr/share/nginx/html
      name: nfs-storage
  volumes:
  - name: nfs-storage
    persistentVolumeClaim:
      claimName: myclaim  # ← Reference PVC