Skip to content

NFS shared storage client configuration

In Kubernetes deployments, shared storage is often required to persist data independent of the Pod lifecycle. A common approach involves configuring a dedicated node (such as node 200) as an NFS client to serve as a persistent volume backend.^[400-devops-06-kubernetes-k8s-learning-linux-04-jenkins-readme.md]

Installation and Service Management

The client configuration begins with the installation of the necessary utilities. On the designated storage node, the nfs-utils package must be installed using yum.^[400-devops-06-kubernetes-k8s-learning-linux-04-jenkins-readme.md] Following installation, the NFS service should be started and enabled to ensure it persists across system reboots.^[400-devops-06-kubernetes-k8s-learning-linux-04-jenkins-readme.md]

Directory Setup

To facilitate the sharing of data, a specific directory structure must be created on the server to act as the mount point or export root.^[400-devops-06-kubernetes-k8s-learning-linux-04-jenkins-readme.md] Commonly, this is located within a standardized data path, such as /data/nfs-volume.^[400-devops-06-kubernetes-k8s-learning-linux-04-jenkins-readme.md]

Configuration

The behavior of the NFS service is controlled via the /etc/exports file^[400-devops-06-kubernetes-k8s-learning-linux-04-jenkins-readme.md]. While specific export rules are not detailed in the source, the administrator must edit this file to define which directories are shared and with what permissions.

Sources

^[400-devops-06-kubernetes-k8s-learning-linux-04-jenkins-readme.md]