What is the main reason to use persistent volumes instead of defining volumes inside every pod spec?
Persistent volumes centralize storage management so users do not need to repeat storage configuration in every pod and changes do not require editing many pod definitions.
What is a persistent volume in Kubernetes?
A persistent volume is a cluster wide storage resource created and managed by an administrator that applications can use through claims.
How do users request or carve out storage from the persistent volume pool?
Users create persistent volume claims which select and bind to available persistent volumes.
What key fields are defined in a persistent volume spec in the lecture example?
The example defines accessModes capacity and a volume type such as hostPath.
Why is hostPath used only as a simple example and not recommended for production?
hostPath relies on a local node directory and is not suitable for reliable multi node production storage.