How to Restore a PVC from NFS and Attach to a Pod

A clear, unique guide that shows how to Restore a PVC from NFS and attach to a Pod with real commands, steps, and checks to keep your Kubernetes data safe. Our 24/7 Live Support Team is always here to help you.

If you’ve ever watched an app fail because its data vanished after a pod crash, you know that painful moment. In Kubernetes, your data lives only if your persistent storage lives. That’s why learning how to Restore a PVC from NFS and attach to a Pod can save you from long nights, broken deployments, and angry customers.

Let’s walk through the process in a simple, everyday way.

What Exactly Is NFS?

Before anything else, it helps to understand the storage you’re working with.
NFS (Network File System) lets multiple systems read and write data over a network as if it were a local disk. Even though it’s decades old, it’s reliable, open, cost-friendly, and predictable. Because of that, many Kubernetes clusters still depend on it for stateful apps.

Steps

Create a PersistentVolume (PV)

Once your new cluster is ready, attach the same NFS instance as your storage backend. Then create a PV using your previous PVC details. Update the YAML with your actual NFS path, IP, and PVC name.

apiVersion: v1

kind: PersistentVolume

metadata:

name: pvc-477f63d2-9cf2-42ff-bf99-1e5b74c5f0f9

annotations:

pv.kubernetes.io/provisioned-by: nfs.csi.k8s.io

finalizers:

- kubernetes.io/pv-protection

spec:

capacity:

storage: 8Gi

accessModes:

- ReadWriteOnce

persistentVolumeReclaimPolicy: Retain

storageClassName: nfs-csi

volumeMode: Filesystem

claimRef:

name: data-pbms-postgresql-0

namespace: dev

csi:

driver: nfs.csi.k8s.io

volumeHandle: 172.29.68.134#srv/nfs/dev#dev-data-pbms-postgresql-0-pvc-477f63d2-9cf2-42ff-bf99-1e5b74c5f0f9

volumeAttributes:

server: 172.29.68.134

share: /srv/nfs/dev

subDir: dev-data-pbms-postgresql-0-pvc-477f63d2-9cf2-42ff-bf99-1e5b74c5f0f9

mountPermissions: '0777'

Apply the file:

kubectl apply -f pv.yaml -n dev

Your PV should now appear in Available state.

At this point, you’re halfway through the process of learning how to Restore a PVC from NFS and attach to a Pod safely.

Deploy Services With Old Secrets

While redeploying your apps, make sure the old database credentials and passwords are put back into Kubernetes. Without these, your restored PVC won’t mean much.

Here’s a small credential example:

odooPassword: <odooPassword>

postgresql:

auth:

database: <databaseName>

username: <username>

password: <dbPassword>

postgresPassword: <postgresPassword>

Replace placeholders with the original values.

After your services come up, Kubernetes automatically binds the PVC to the PV, letting you fully Restore a PVC from NFS and attach to a Pod without losing data.

Validate the Application

Open your app, test logins, check data, and confirm everything loads from NFS. Once verified, you’ve successfully pulled off the process to Restore a PVC from NFS and attach to a Pod, and your system is back on its feet.

Conclusion

The ability to Restore a PVC from NFS and attach to a Pod isn’t just a backup trick. It’s a survival skill for anyone running stateful workloads on Kubernetes. With the right checks, correct PV configuration, and old secrets restored, your apps will run just as they did before the failure, maybe even better because you now know how to recover them.