kubernetes資料持久化StorageClass動態供給(二)

梨花海棠發表於2022-11-28

儲存類的好處之一便是支援PV的動態供給，它甚至可以直接被視作為PV的建立模版，使用者用到永續性儲存時，需要透過建立PVC來繫結匹配的PV，此類操作需求較大，或者當管理員手動建立的PV無法滿足PVC的所有需求時，系統按PVC的需求標準動態建立適配的PV會為儲存管理帶來極大的靈活性，不過僅那些屬於StorageClass的PVC和PV才能產生繫結關係，即沒有指定StorageClass的PVC只能繫結同類的PV。
儲存類物件的名稱至關重要，它是使用者呼叫的標識，建立儲存類物件時，除了名稱之外，還需要為其定義三個關鍵欄位。provisioner、parameter和reclaimPolicy。
所以kubernetes提供了一種可以動態分配的工作機制，可用自動建立PV，該機制依賴於StorageClass的API，將某個儲存節點劃分1T給kubernetes使用，當使用者申請5Gi的PVC時，會自動從這1T的儲存空間去建立一個5Gi的PV，而後自動與之進行關聯繫結。
動態PV供給的啟用需要事先建立一個儲存類，不同的Provisoner的建立方法各有不同，並非所有的儲存卷外掛都由Kubernetes內建支援PV動態供給。

2.基於NFS實現動態供應

由於kubernetes內部不包含NFS驅動，所以需要使用外部驅動nfs-subdir-external-provisioner是一個自動供應器，它使用NFS服務端來支援動態供應。
NFS-subdir-external- provisioner例項負責監視PersistentVolumeClaims請求StorageClass，並自動為它們建立NFS所支援的PresistentVolumes。
GitHub地址: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner

2.1 準備NFS服務端的共享目錄

這裡的意思是要把哪個目錄給kubernetes來使用。把目錄共享出來。

[root@kn-server-node02-15 ~]# ll /data/
總用量 0
[root@kn-server-node02-15 ~]# showmount -e 10.0.0.15
Export list for 10.0.0.15:
/data        10.0.0.0/24

2.2 安裝NFS-Server驅動。

首先建立RBAC許可權。

[root@kn-server-master01-13 nfs-provisioner]# cat nfs-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
[root@kn-server-master01-13 nfs-provisioner]# kubectl apply -f nfs-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

2.3 部署NFS-Provisioner

[root@kn-server-master01-13 nfs-provisioner]# cat nfs-provisioner-deploy.yaml 
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nfs-client-provisioner
  labels:
    app: nfs-client-provisioner
  # replace with namespace where provisioner is deployed
  namespace: default
spec:
  replicas: 1
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app: nfs-client-provisioner
  template:
    metadata:
      labels:
        app: nfs-client-provisioner
    spec:
      serviceAccountName: nfs-client-provisioner
      containers:
        - name: nfs-client-provisioner
          image: k8s.gcr.io/sig-storage/nfs-subdir-external-provisioner:v4.0.2  映象在國內是拉取不到的，因此為下載下來了放在我的docker hub。 替換為lihuahaitang/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   NFS-Provisioner的名稱，後續StorageClassName要與該名稱保持一致
            - name: NFS_SERVER    NFS伺服器的地址
              value: 10.0.0.15  
            - name: NFS_PATH
              value: /data
      volumes:
        - name: nfs-client-root
          nfs:
            server: 10.0.0.15
            path: /data
[root@kn-server-master01-13 nfs-provisioner]# kubectl apply -f nfs-provisioner-deploy.yaml 
deployment.apps/nfs-client-provisioner created


Pod正常執行。
[root@kn-server-master01-13 nfs-provisioner]# kubectl get pods
NAME                                      READY   STATUS    RESTARTS   AGE
nfs-client-provisioner-57d6d9d5f6-dcxgq   1/1     Running   0          2m25s

describe檢視Pod詳細資訊；
[root@kn-server-master01-13 nfs-provisioner]# kubectl describe pods nfs-client-provisioner-57d6d9d5f6-dcxgq 
Name:         nfs-client-provisioner-57d6d9d5f6-dcxgq
Namespace:    default
Priority:     0
Node:         kn-server-node02-15/10.0.0.15
Start Time:   Mon, 28 Nov 2022 11:19:33 +0800
Labels:       app=nfs-client-provisioner
              pod-template-hash=57d6d9d5f6
Annotations:  <none>
Status:       Running
IP:           192.168.2.82
IPs:
  IP:           192.168.2.82
Controlled By:  ReplicaSet/nfs-client-provisioner-57d6d9d5f6
Containers:
  nfs-client-provisioner:
    Container ID:   docker://b5ea240a8693185be681714747f8e0a9f347492a24920dd68e629effb3a7400f
    Image:          k8s.gcr.io/sig-storage/nfs-subdir-external-provisioner:v4.0.2  映象來自k8s.gcr.io
    Image ID:       docker-pullable://k8s.gcr.io/sig-storage/nfs-subdir-external-provisioner@sha256:63d5e04551ec8b5aae83b6f35938ca5ddc50a88d85492d9731810c31591fa4c9
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Mon, 28 Nov 2022 11:20:12 +0800
    Ready:          True
    Restart Count:  0
    Environment:
      PROVISIONER_NAME:  k8s-sigs.io/nfs-subdir-external-provisioner
      NFS_SERVER:        10.0.0.15
      NFS_PATH:          /data
    Mounts:
      /persistentvolumes from nfs-client-root (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-q2z8w (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  PodScheduled      True 
Volumes:
  nfs-client-root:
    Type:      NFS (an NFS mount that lasts the lifetime of a pod)
    Server:    10.0.0.15
    Path:      /data
    ReadOnly:  false
  kube-api-access-q2z8w:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type    Reason     Age    From               Message
  ----    ------     ----   ----               -------
  Normal  Scheduled  3m11s  default-scheduler  Successfully assigned default/nfs-client-provisioner-57d6d9d5f6-dcxgq to kn-server-node02-15
  Normal  Pulling    3m11s  kubelet            Pulling image "k8s.gcr.io/sig-storage/nfs-subdir-external-provisioner:v4.0.2"
  Normal  Pulled     2m32s  kubelet            Successfully pulled image "k8s.gcr.io/sig-storage/nfs-subdir-external-provisioner:v4.0.2" in 38.965869132s
  Normal  Created    2m32s  kubelet            Created container nfs-client-provisioner
  Normal  Started    2m32s  kubelet            Started container nfs-client-provisioner

2.4 建立StorageClass

建立NFS StorageClass動態供應商。

[root@kn-server-master01-13 nfs-provisioner]# cat storageclass.yaml 
apiVersion: storage.k8s.io/v1
kind: StorageClass    型別為storageclass
metadata:
  name: nfs-provisioner-storage    PVC申請時需明確指定的storageclass名稱
  annotations:
    storageclass.kubernetes.io/is-default-class: "true"
provisioner: k8s-sigs.io/nfs-subdir-external-provisioner  供應商名稱，必須和上面建立的"PROVISIONER_NAME"保持一致
parameters:
  archiveOnDelete: "false" 如果值為false，刪除pvc後也會刪除目錄內容，"true"則會對資料進行保留
  pathPattern: "${.PVC.namespace}/${.PVC.name}" 建立目錄路徑的模板，預設為隨機命名。
[root@kn-server-master01-13 nfs-provisioner]# kubectl apply -f storageclass.yaml 
storageclass.storage.k8s.io/nfs-provisioner-storage created

storage簡寫sc
[root@kn-server-master01-13 nfs-provisioner]# kubectl get sc
NAME                      PROVISIONER                                   RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
nfs-provisioner-storage   k8s-sigs.io/nfs-subdir-external-provisioner   Delete          Immediate           false                  3s

describe檢視配詳細資訊。
[root@kn-server-master01-13 nfs-provisioner]# kubectl describe sc 
Name:            nfs-provisioner-storage
IsDefaultClass:  Yes
Annotations:     kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"storage.k8s.io/v1","kind":"StorageClass","metadata":{"annotations":{"storageclass.kubernetes.io/is-default-class":"true"},"name":"nfs-provisioner-storage"},"parameters":{"archiveOnDelete":"false","pathPattern":"${.PVC.namespace}/${.PVC.name}"},"provisioner":"k8s-sigs.io/nfs-subdir-external-provisioner"}
,storageclass.kubernetes.io/is-default-class=true
Provisioner:           k8s-sigs.io/nfs-subdir-external-provisioner
Parameters:            archiveOnDelete=false,pathPattern=${.PVC.namespace}/${.PVC.name}
AllowVolumeExpansion:  <unset>
MountOptions:          <none>
ReclaimPolicy:         Delete
VolumeBindingMode:     Immediate
Events:                <none>

2.5 建立PVC，自動關聯PV

[root@kn-server-master01-13 nfs-provisioner]# cat nfs-pvc-test.yaml 
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: nfs-pvc-test
spec:
  storageClassName: "nfs-provisioner-storage"
  accessModes:
  - ReadWriteMany
  resources:
    requests:
      storage: 0.5Gi

這裡的PV的名字是隨機的，資料的儲存路徑是根據pathPattern來定義的。
[root@kn-server-node02-15 data]# ls
default
[root@kn-server-node02-15 data]# ll default/
總用量 0
drwxrwxrwx 2 root root 6 11月 28 13:56 nfs-pvc-test
[root@kn-server-master01-13 pv]# kubectl get pv
pvc-8ed67f7d-d829-4d87-8c66-d8a85f50772f   512Mi      RWX            Delete           Bound         default/nfs-pvc-test   nfs-provisioner-storage            5m19s
[root@kn-server-master01-13 nfs-provisioner]# kubectl describe pv pvc-8ed67f7d-d829-4d87-8c66-d8a85f50772f
Name:            pvc-8ed67f7d-d829-4d87-8c66-d8a85f50772f
Labels:          <none>
Annotations:     pv.kubernetes.io/provisioned-by: k8s-sigs.io/nfs-subdir-external-provisioner
Finalizers:      [kubernetes.io/pv-protection]
StorageClass:    nfs-provisioner-storage
Status:          Bound
Claim:           default/nfs-pvc-test
Reclaim Policy:  Delete
Access Modes:    RWX
VolumeMode:      Filesystem
Capacity:        512Mi
Node Affinity:   <none>
Message:         
Source:
    Type:      NFS (an NFS mount that lasts the lifetime of a pod)
    Server:    10.0.0.15
    Path:      /data/default/nfs-pvc-test
    ReadOnly:  false
Events:        <none>


describe可用看到更詳細的資訊
root@kn-server-master01-13 nfs-provisioner]# kubectl describe pvc 
Name:          nfs-pvc-test
Namespace:     default
StorageClass:  nfs-provisioner-storage
Status:        Bound
Volume:        pvc-8ed67f7d-d829-4d87-8c66-d8a85f50772f
Labels:        <none>
Annotations:   pv.kubernetes.io/bind-completed: yes
               pv.kubernetes.io/bound-by-controller: yes
               volume.beta.kubernetes.io/storage-provisioner: k8s-sigs.io/nfs-subdir-external-provisioner
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      512Mi    定義的儲存大小
Access Modes:  RWX    卷的讀寫
VolumeMode:    Filesystem
Used By:       <none>
Events:
  Type    Reason                 Age   From                                                                                                                      Message
  ----    ------                 ----  ----                                                                                                                      -------
  Normal  ExternalProvisioning   13m   persistentvolume-controller                                                                                               waiting for a volume to be created, either by external provisioner "k8s-sigs.io/nfs-subdir-external-provisioner" or manually created by system administrator
  Normal  Provisioning           13m   k8s-sigs.io/nfs-subdir-external-provisioner_nfs-client-provisioner-57d6d9d5f6-dcxgq_259532a3-4dba-4183-be6d-8e8b320fc778  External provisioner is provisioning volume for claim "default/nfs-pvc-test"
  Normal  ProvisioningSucceeded  13m   k8s-sigs.io/nfs-subdir-external-provisioner_nfs-client-provisioner-57d6d9d5f6-dcxgq_259532a3-4dba-4183-be6d-8e8b320fc778  Successfully provisioned volume pvc-8ed67f7d-d829-4d87-8c66-d8a85f50772f

2.6 建立Pod，測試資料是否持久。

[root@kn-server-master01-13 nfs-provisioner]# cat nginx-pvc-test.yaml
apiVersion: v1
kind: Pod
metadata:
  name: nginx-sc
spec:
  containers:
  - name: nginx
    image: nginx
    volumeMounts:
    - name: nginx-page
      mountPath: /usr/share/nginx/html
  volumes:
  - name: nginx-page
    persistentVolumeClaim:
      claimName: nfs-pvc-test
[root@kn-server-master01-13 nfs-provisioner]# kubectl apply -f nginx-pvc-test.yaml 
pod/nginx-sc created

[root@kn-server-master01-13 nfs-provisioner]# kubectl describe pvc
Name:          nfs-pvc-test
Namespace:     default
StorageClass:  nfs-provisioner-storage
Status:        Bound
Volume:        pvc-8ed67f7d-d829-4d87-8c66-d8a85f50772f
Labels:        <none>
Annotations:   pv.kubernetes.io/bind-completed: yes
               pv.kubernetes.io/bound-by-controller: yes
               volume.beta.kubernetes.io/storage-provisioner: k8s-sigs.io/nfs-subdir-external-provisioner
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      512Mi
Access Modes:  RWX
VolumeMode:    Filesystem
Used By:       nginx-sc   可以看到的是nginx-sc這個Pod在使用這個PVC。

和上面名稱是一致的。
[root@kn-server-master01-13 nfs-provisioner]# kubectl get pods nginx-sc
NAME       READY   STATUS    RESTARTS   AGE
nginx-sc   1/1     Running   0          2m43s

嘗試寫入資料
[root@kn-server-node02-15 data]# echo "haitang" > /data/default/nfs-pvc-test/index.html

訪問測試。
[root@kn-server-master01-13 nfs-provisioner]# curl 192.168.2.83
haitang

Kubernetes 持久化資料儲存 StorageClass
2021-09-08
持久化
細述Kubernetes中的StorageClass和動態卷供給
2019-04-27
基於NFS的PV動態供給(StorageClass)
2019-05-12
NFS
kubernetes資料持久化PV-PVC詳解（一）
2022-11-27
持久化
Redis資料持久化—RDB持久化與AOF持久化
2021-05-20
Redis持久化
MVVM的資料持久化（二）——ROOM的使用
2018-11-07
MVVM持久化OOM
從0到1使用Kubernetes系列（六）：資料持久化實戰
2019-04-10
持久化
fabric資料持久化
2019-03-08
持久化
Docker資料持久化
2024-09-08
Docker持久化
Redis 資料持久化
2021-04-07
Redis持久化
K8S學習筆記之Kubernetes資料持久化方案
2019-03-20
K8S筆記持久化
（三）Kubernetes---持久化儲存
2020-12-10
持久化
Docker之資料持久化
2018-12-12
Docker持久化
【Unity】資料持久化PlayerPrefs
2024-10-10
Unity持久化
Redis的資料持久化
2022-12-20
Redis持久化
資料的序列化&持久化
2019-06-27
持久化
Redis原理二：持久化
2018-09-04
Redis持久化
iOS資料持久化設計
2019-03-04
iOS持久化
鴻蒙資料持久化sqlite
2024-10-11
鴻蒙持久化SQLite
可持久化資料結構
2024-07-26
持久化資料結構
Docker --volume-資料持久化
2020-12-23
Docker持久化
詳解 ZooKeeper 資料持久化
2021-03-18
持久化
Kubernetes 跨 StorageClass 遷移 Persistent Volumes 完全指南
2022-06-25
事務狀態持久化
2019-08-14
持久化
Kubernetes的故事之持久化儲存(十)
2022-01-26
持久化
TopoLVM: 基於LVM的Kubernetes本地持久化方案，容量感知，動態建立PV，輕鬆使用本地磁碟
2022-06-26
LVM持久化
可持久化資料結構1
2024-08-20
持久化資料結構
iOS資料持久化儲存-CoreData
2018-04-04
iOS持久化
Milvus 2.0 資料插入與持久化
2022-03-31
持久化
HarmonyOS資料管理與應用資料持久化（一）
2023-11-01
持久化
利用Kubernetes實現容器的持久化儲存
2019-01-30
持久化
鴻蒙首選項資料持久化
2024-10-10
鴻蒙持久化
redis原始碼分析（五）：資料持久化
2021-09-09
Redis原始碼持久化
Kubernetes跨StorageClass遷移，切換Rainbond預設SC
2023-10-26
AI
[Kubernetes]5. k8s叢集StatefulSet詳解,以及資料持久化（SC PV PVC）
2024-06-03
K8S持久化
星環科技自研技術，加速大資料從持久化、統一化、資產化、業務化到生態化
2023-04-14
大資料持久化
k8s使用glusterfs實現動態持久化儲存
2018-12-17
K8S持久化
k8s使用ceph實現動態持久化儲存
2018-12-17
K8S持久化