PersistentVolume YAML Generator

A PersistentVolume (PV) is cluster storage that an administrator provisions and that users claim through PersistentVolumeClaims. It is cluster-scoped, so it lives outside any namespace. The PersistentVolume YAML Generator writes that manifest from a form so you do not have to recall the core/v1 schema.

You set the PV name and, optionally, labels. Then you define its capacity (for example 10Gi), volumeMode (Filesystem or Block), the access modes it supports, and the reclaim policy (Retain, Delete or Recycle). Finally you pick a volume source - hostPath for a node directory, nfs for an NFS share, or local for a local disk that requires node affinity - and fill in the relevant fields. The resulting YAML is valid core/v1.

The name is validated as an RFC 1123 label, capacity is required, at least one access mode is required, and the chosen volume source must have its required fields. Problems are reported in a clear panel. Everything runs locally and nothing is uploaded.

• Capacity - storage size such as 10Gi.
• volumeMode - Filesystem or Block.
• Access modes - ReadWriteOnce, ReadOnlyMany, ReadWriteMany (comma separated).
• Reclaim policy - Retain, Delete or Recycle.
• Volume sources - hostPath, nfs and local (with node affinity).
• storageClassName - optional; omit to leave unset.
• Validation - RFC 1123 name and required fields.
• Copy / Download / Print - get pv.yaml wherever you need it.

1. Name the PV. Type a valid RFC 1123 name.
2. Set capacity and access modes. e.g. 10Gi and ReadWriteOnce.
3. Pick a reclaim policy. Retain, Delete or Recycle.
4. Choose a volume source. hostPath, nfs or local.
5. Fill the source fields. path, or server+path, or path+node for local.
6. Watch the preview and export.

Example 1 - hostPath. capacity 10Gi, accessModes ReadWriteOnce, hostPath /mnt/data.

Example 2 - nfs. server nfs.example.com, path /exports/data.

Example 3 - local. path /mnt/disks/ssd1 with node node-1.

Example 4 - Retain. reclaimPolicy Retain keeps data after release.

Example 5 - Storage class. storageClassName fast for dynamic binding.

• Correct schema - valid core/v1 PersistentVolume.
• Multiple sources - hostPath, nfs and local handled.
• Validated - names and required fields checked.
• Clean output - empty fields omitted.
• Private - everything runs in the browser.
• Copy, download or print - get the manifest where you need it.