|NO.Z.00248|——————————|CloudNative|——|KuberNetes&存储进阶.V14|——|Ceph.v08|ceph测试|PVC扩容|

一、PVC扩容

### --- PVC扩容说明

~~~     文件共享类型的PVC扩容需要k8s 1.15+
~~~     块存储类型的PVC扩容需要k8s 1.16+
~~~     PVC扩容需要开启ExpandCSIVolumes，新版本的k8s已经默认打开了这个功能，
~~~     可以查看自己的k8s版本是否已经默认打开了该功能：

### --- 如果default为true就不需要打开此功能，如果default为false，需要开启该功能。

[root@k8s-master01 cephfs]# kube-apiserver -h |grep ExpandCSIVolumes
                                                     ExpandCSIVolumes=true|false (BETA - default=true)

二、扩容文件共享型PVC

### --- 找到刚才创建的文件共享型StorageClass，
~~~     将allowVolumeExpansion设置为true（新版rook默认为true，如果不为true更改后执行kubectl replace即可）：

[root@k8s-master01 ~]# cd /root/rook/cluster/examples/kubernetes/ceph/csi/cephfs
[root@k8s-master01 cephfs]# vim storageclass.yaml 
reclaimPolicy: Delete
allowVolumeExpansion: true      // 设置为true
mountOptions:

三、找到第六章创建的pvc

### --- 扩容PVC
~~~     注：将大小修改为2Gi，之前是1Gi
~~~     保存退出

[root@k8s-master01 cephfs]# kubectl  get pvc -n kube-system
NAME         STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
cephfs-pvc   Bound    pvc-2ca6f479-124b-464a-85ab-cf307109f907   1Gi        RWX            rook-cephfs    12m
[root@k8s-master01 cephfs]# kubectl  edit pvc cephfs-pvc -n kube-system
spec:
  accessModes:
  - ReadWriteMany
  resources:
    requests:
      storage: 2Gi                  

四、查看PV和PVC的大小

[root@k8s-master01 cephfs]# kubectl  get pvc -n kube-system
NAME         STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
cephfs-pvc   Bound    pvc-2ca6f479-124b-464a-85ab-cf307109f907   2Gi        RWX            rook-cephfs    15m
[root@k8s-master01 cephfs]#  kubectl  get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                    STORAGECLASS      REASON   AGE
pvc-2ca6f479-124b-464a-85ab-cf307109f907   2Gi        RWX            Delete           Bound    kube-system/cephfs-pvc   rook-cephfs                15m
pvc-a22e54cf-9d96-4070-b3a7-90a2fa73c249   20Gi       RWO            Delete           Bound    default/mysql-pv-claim   rook-ceph-block            48m

五、查看容器内是否已经完成扩容

~~~     # 同样的方案可以定义自己需求扩容的大小

[root@k8s-master01 cephfs]# kubectl get po -n kube-system -l k8s-app=kube-registry -owide
NAME                             READY   STATUS    RESTARTS   AGE   IP               NODE           NOMINATED NODE   READINESS GATES
kube-registry-66d4c7bf47-b87w4   1/1     Running   0          17m   172.27.14.204    k8s-node02     <none>           <none>
kube-registry-66d4c7bf47-tmp4c   1/1     Running   0          17m   172.17.125.22    k8s-node01     <none>           <none>
kube-registry-66d4c7bf47-tvxvb   1/1     Running   0          17m   172.25.244.212   k8s-master01   <none>           <none>
[root@k8s-master01 cephfs]# kubectl exec -ti kube-registry-66d4c7bf47-b87w4 -n kube-system -- df -Th | grep "/var/lib/registry"
                     ceph            2.0G         0      2.0G   0% /var/lib/registry

---

 

 

 

 

 

 

 

 

 

---

Walter Savage Landor:strove with none,for none was worth my strife.Nature I loved and, next to Nature, Art:I warm'd both hands before the fire of life.It sinks, and I am ready to depart

                                                                                                                                                   ——W.S.Landor

---