1. 概述

在日常學(xué)習(xí)與企業(yè)內(nèi)網(wǎng)環(huán)境中，可能并沒有條件使用Ceph等分布式存儲艘希，這時可以使用NFS作為StorageClass侠坎。

NFS代表網(wǎng)絡(luò)文件系統(tǒng)（Network File System）庄新，它是一種允許計算機(jī)通過網(wǎng)絡(luò)共享文件和存儲設(shè)備的協(xié)議偿短。

2. 環(huán)境說明

本文nfs server所在服務(wù)器的操作系統(tǒng)為Ubuntu 22.04.2, IP為192.168.3.10

kubernetes版本為1.27.2
kubernetes節(jié)點(diǎn)的操作系統(tǒng)為RockyLinux 9.2 x64

3. k8s集群外部署NFS server

1. 安裝nfs server

apt install -y nfs-kernel-server 

2. 配置nfs server

mkdir /data/nfs
chmod a+rw /data/nfs/
echo '/data/nfs *(rw,sync,no_subtree_check,no_root_squash,insecure)' >> /etc/exports
# 使配置生效
exportfs -r
# 查看當(dāng)前配置
exportfs

systemctl restart rpcbind
systemctl enable rpcbind
systemctl restart nfs-server
systemctl enable nfs-server

# 查看rpc服務(wù)的注冊情況
rpcinfo -p localhost |grep nfs
showmount -e 192.168.3.10

4. k8s集群內(nèi)創(chuàng)建Storage class

官方文檔: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner

4.1 所有k8s節(jié)點(diǎn)安裝nfs client

# centos/rockylinux
yum install -y nfs-utils

4.2 為NFS設(shè)置rbac

創(chuàng)建文件rbac.yaml

apiVersion: v1
kind: ServiceAccount
metadata:
  name: nfs-client-provisioner
  # replace with namespace where provisioner is deployed
  namespace: default
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: nfs-client-provisioner-runner
rules:
  - apiGroups: [""]
    resources: ["nodes"]
    verbs: ["get", "list", "watch"]
  - apiGroups: [""]
    resources: ["persistentvolumes"]
    verbs: ["get", "list", "watch", "create", "delete"]
  - apiGroups: [""]
    resources: ["persistentvolumeclaims"]
    verbs: ["get", "list", "watch", "update"]
  - apiGroups: ["storage.k8s.io"]
    resources: ["storageclasses"]
    verbs: ["get", "list", "watch"]
  - apiGroups: [""]
    resources: ["events"]
    verbs: ["create", "update", "patch"]
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: run-nfs-client-provisioner
subjects:
  - kind: ServiceAccount
    name: nfs-client-provisioner
    # replace with namespace where provisioner is deployed
    namespace: default
roleRef:
  kind: ClusterRole
  name: nfs-client-provisioner-runner
  apiGroup: rbac.authorization.k8s.io
---
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: leader-locking-nfs-client-provisioner
  # replace with namespace where provisioner is deployed
  namespace: default
rules:
  - apiGroups: [""]
    resources: ["endpoints"]
    verbs: ["get", "list", "watch", "create", "update", "patch"]
---
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: leader-locking-nfs-client-provisioner
  # replace with namespace where provisioner is deployed
  namespace: default
subjects:
  - kind: ServiceAccount
    name: nfs-client-provisioner
    # replace with namespace where provisioner is deployed
    namespace: default
roleRef:
  kind: Role
  name: leader-locking-nfs-client-provisioner
  apiGroup: rbac.authorization.k8s.io

kubectl apply -f rbac.yaml

輸出

serviceaccount/nfs-client-provisioner created
clusterrole.rbac.authorization.k8s.io/nfs-client-provisioner-runner created
clusterrolebinding.rbac.authorization.k8s.io/run-nfs-client-provisioner created
role.rbac.authorization.k8s.io/leader-locking-nfs-client-provisioner created
rolebinding.rbac.authorization.k8s.io/leader-locking-nfs-client-provisioner created

4.3 創(chuàng)建nfs subdir external provisioner

創(chuàng)建文件nfs-subdir-external-provisioner.yaml

kind: Deployment
apiVersion: apps/v1
metadata:
  name: nfs-client-provisioner
spec:
  replicas: 1
  selector:
    matchLabels:
      app: nfs-client-provisioner
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: nfs-client-provisioner
    spec:
      serviceAccountName: nfs-client-provisioner
      containers:
        - name: nfs-client-provisioner
          # image: registry.k8s.io/sig-storage/nfs-subdir-external-provisioner:v4.0.2
          image: k8s.dockerproxy.com/sig-storage/nfs-subdir-external-provisioner:v4.0.2
          volumeMounts:
            - name: nfs-client-root
              mountPath: /persistentvolumes
          env:
            - name: PROVISIONER_NAME
              value: k8s-sigs.io/nfs-subdir-external-provisioner
            - name: NFS_SERVER
              # value: <YOUR NFS SERVER HOSTNAME>
              value: 192.168.3.10
            - name: NFS_PATH
              # value: /var/nfs
              value: /data/nfs
      volumes:
        - name: nfs-client-root
          nfs:
            # server: <YOUR NFS SERVER HOSTNAME>
            server: 192.168.3.10
            path: /data/nfs

kubectl apply -f nfs-subdir-external-provisioner.yaml

4.4 部署storage class

創(chuàng)建文件nfs-storage-class.yaml

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: nfs-client
provisioner: k8s-sigs.io/nfs-subdir-external-provisioner # or choose another name, must match deployment's env PROVISIONER_NAME'
parameters:
  pathPattern: "${.PVC.namespace}/${.PVC.annotations.nfs.io/storage-path}" # 此處也可以使用 "${.PVC.namespace}/${.PVC.name}" 來使用pvc的名稱作為nfs中真實目錄名稱
  onDelete: delete

kubectl apply -f nfs-storage-class.yaml

5. 測試nfs storage class

5.1 創(chuàng)建一個PVC

創(chuàng)建文件nfs-pvc.yaml

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: test-claim
  annotations:
    nfs.io/storage-path: "test-path" # not required, depending on whether this annotation was shown in the storage class description
spec:
  storageClassName: nfs-client
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 50Mi

kubectl apply -f nfs-pvc.yaml

查看pvc

kubectl get pvc

輸出

NAME         STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
test-claim   Bound    pvc-e9a9f6ad-45f8-4e3f-9b1e-abdc5f59c7ef   50Mi       RWX            nfs-client     11s

5.2 在NFS server查看

登錄服務(wù)器192.168.3.10

可以看到在/data/nfs/目錄下有一個default目錄,這表示default命名空間

default目錄下有一個test-path目錄，這個就是創(chuàng)建pvc時在annotations指定的 nfs.io/storage-path: "test-path"凯旋；

tree /data/nfs/

/data/nfs/
├── default
│   └── test-path