“Kubernetes Storage: Creating Dynamic Storage StorageClass Based on NFS”

# Add repository
root@k8s-master-32:~# helm repo add moikot https://moikot.github.io/helm-charts
root@k8s-master-32:~# helm repo update

#Install chart
helm install --generate-name \
--set nfs.server=192.168.1.38 \
--set nfs.path=/data/k8s/volumes \
--set storageClass.reclaimPolicy=Delete \
--set image.repository=registry.cn-beijing.aliyuncs.com/pylixm/nfs-subdir-external-provisioner \
--set image.tag=v4.0.0 \
moikot/nfs-client-provisioner --version 1.3.0

The following table lists the possible Configuration parameters and their default values are as shown in the figure below:

Note: Starting from Kubernetes v1.20, the default The metadata.selfLink field has been removed. However, some applications still rely on this field, such as nfs-client-provisioner. If you still want to continue using these apps, you will need to re-enable this field in your current environment. However, in the current K8S 1.24.17 version, turning on this field will cause kube-apiserver to fail to start normally. After testing, the default quay.io/external_storage/nfs-client-provisioner:latest image was modified to a provisioner that is not based on the SelfLink function. Mirror, namely registry.cn-beijing.aliyuncs.com/pylixm/nfs-subdir-external-provisioner:v4.0.0

3. Test, create a test-calim pvc

vim test-claim.yaml

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: test-claim
  annotations:
    volume.beta.kubernetes.io/storage-class: "nfs-client" #Can be viewed using the kubectl get storageclasses command
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      Storage: 2Gi

7. Test, create a test-pod Documents

vim test-pod.yaml

Kind: Pod
apiVersion: v1
metadata:
  name: test-pod
spec:
  containers:
  - name: test-pod
    image: busybox:1.24
    command:
      - "/bin/sh"
    args:
      - "-c"
      - "touch /mnt/SUCCESS & amp; & amp; exit 0 || exit 1"
    volumeMounts:
      - name: nfs-pvc
        mountPath: "/mnt"
  restartPolicy: "Never"
  volumes:
    - name: nfs-pvc
      persistentVolumeClaim:
        claimName: test-claim

8. As shown in the picture below, view sharing Directory/data/volumes/v1/, if there is a SUCCESS file below, it means the deployment is successful

2.4. Manually install the nfs client plug-in

1. Download the nfs client resource file

wget https://github.com/kubernetes-retired/external-storage/archive/refs/heads/master.zip
unzip master.zip
cd external-storage-master/nfs-client/deploy/

root@k8s-master-32:~/external-storage-master/nfs-client/deploy# kubectl create -f rbac.yaml

root@k8s-master-32:~/external-storage-master/nfs-client/deploy# kubectl create -f deployment.yaml

vim class.yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: managed-nfs-storage
reclaimPolicy: Delete
provisioner: fuseim.pri/ifs # or choose another name, must match deployment's env PROVISIONER_NAME'
parameters:
  archiveOnDelete: "false"

root@k8s-master-32:~/external-storage-master/nfs-client/deploy# kubectl create -f class.yaml

vim test-claim.yaml

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: test-claim
  annotations:
    volume.beta.kubernetes.io/storage-class: "managed-nfs-storage"
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      Storage: 2Gi

vim test-pod.yaml

Kind: Pod
apiVersion: v1
metadata:
  name: test-pod
spec:
  containers:
  - name: test-pod
    image: busybox:1.24
    command:
      - "/bin/sh"
    args:
      - "-c"
      - "touch /mnt/SUCCESS & amp; & amp; exit 0 || exit 1"
    volumeMounts:
      - name: nfs-pvc
        mountPath: "/mnt"
  restartPolicy: "Never"
  volumes:
    - name: nfs-pvc
      persistentVolumeClaim:
        claimName: test-claim