NFS
Mount an external NFS server or expose an existing PVC as an NFS share.
NFS mounts give you two options: connect to an NFS server that already exists outside Vantage, or expose an existing PVC as an NFS share so it can be mounted from any namespace.
Prerequisites
A Kubernetes cluster in Connected state.
For internal NFS: an existing PVC on the cluster to use as the backing store.
Create an NFS mount
Open Storage
Go to Clusters, select your Kubernetes cluster, then click the Storage tab.
Select the NFS tab
Click NFS at the top of the Storage page.
Click Create NFS
Select a namespace
Choose the namespace this NFS mount will be available in.
Enter a name
Lowercase letters, numbers, and hyphens.
Choose a source mode
External: Mount an NFS server running outside Vantage:
- NFS Server: Hostname or IP address of the NFS server.
- NFS Share Path: Absolute path to the exported share (e.g.
/exports/data).
Internal: Expose an existing PVC as an NFS share:
- Source Namespace: The namespace where the source PVC lives (can differ from the target namespace).
- Source PVC: Select the PVC to export.
Set capacity
Enter the size of the share (e.g. 100Gi). For external sources, this is informational; for internal sources it should match the backing PVC.
Set advanced options (optional)
- Access Modes: Default is ReadWriteMany. Uncheck modes your workloads don't need.
- Read Only: Force all mounts of this share to be read-only.
- Mount Options: Additional NFS mount flags, one per line. Defaults:
nfsvers=4.1,hard,nointr.
Click Create
Success looks like this: the NFS import creates a PVC-backed view of the remote share, and pods can mount it as expected.
Internal NFS is the simplest way to share a PVC across namespaces. Create the PVC in one namespace, then create an internal NFS mount targeting it, pods in any namespace can mount the NFS share.