K8S 的 PV 与 PVC 概念及使用

Crush_ly

已于 2024-08-25 21:09:19 修改

阅读量541

点赞数 25

分类专栏： K8S合集文章标签： kubernetes 云原生

于 2024-08-25 21:08:11 首次发布

本文链接：https://blog.csdn.net/m0_37660354/article/details/141534958

版权

K8S合集专栏收录该内容

9 篇文章 0 订阅

订阅专栏

PV 与 PVC 概念：

pv: persist volume 不存在namespace

pvc: persist volume claim 存在namespace 隔离

pod 里的pvc 只是定义了一个名字，链接到了所匹配到的pvc ，pvc 通过指定类型来绑定到某一个pv 上

不同的存储集群会与不同的pv类型以及对应的配置参数。重点讲解nfs 类型

apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv0003
spec:
  capacity:
    storage: 5Gi
  volumeMode: Filesystem
  accessModes:
    - ReadWriteOnce
  persistentVolumeReclaimPolicy: Recycle
  storageClassName: slow
  mountOptions:
    - hard
    - nfsvers=4.1
  nfs:
    path: /data/nfs
    server: 192.168.56.110

persistentVolumeReclaimPolicy 回收策略：

Current reclaim policies are:

Retain -- manual reclamation（保留策略，除非手动清理）
Recycle -- basic scrub (rm -rf /thevolume/*) 回收，自动清理变成可用
Delete -- associated storage asset such as AWS EBS or GCE PD volume is deleted

Currently, only NFS and HostPath support recycling. AWS EBS and GCE PD volumes support deletion 驱动支持这一策略才能使用，清理

PersistentVolumes having Delete reclaim policy are deleted only after the backing storage are deleted.只有当块存储被删除后，pv 才会被删除

Access Modes 访问策略

In the CLI, the access modes are abbreviated to:

RWO - ReadWriteOnce
ROX - ReadOnlyMany
RWX - ReadWriteMany
RWOP - ReadWriteOncePod

ReadWriteOnce

the volume can be mounted as read-write by a single node. ReadWriteOnce access mode still can allow multiple pods to access the volume when the pods are running on the same node.

ReadOnlyMany

the volume can be mounted as read-only by many nodes.

ReadWriteMany

the volume can be mounted as read-write by many nodes.

ReadWriteOncePod

FEATURE STATE: Kubernetes v1.27 [beta]

the volume can be mounted as read-write by a single Pod. Use ReadWriteOncePod access mode if you want to ensure that only one pod across the whole cluster can read that PVC or write to it. This is only supported for CSI volumes and Kubernetes version 1.22+.

Phase pv 的状态

A PersistentVolume will be in one of the following phases:

Available： 可用状态，未被pvc 绑定

a free resource that is not yet bound to a claim

Bound ：绑定状态，已经被pvc绑定

the volume is bound to a claim

Released： pvc 已经被删除，资源还未被重新使用

the claim has been deleted, but the associated storage resource is not yet reclaimed by the cluster

Failed ：清理回收失败

the volume has failed its (automated) reclamation You can see the name of the PVC bound to the PV using kubectl describe persistentvolume <name>

创建pv:

apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv0001
spec:
  capacity:
    storage: 5Gi
  volumeMode: Filesystem
  accessModes:
    - ReadWriteMany
  persistentVolumeReclaimPolicy: Recycle
  storageClassName: nfs-slow
  mountOptions:
    - hard
    - nfsvers=4.1
  nfs:
    path: /data/nfs/k8s-data
    server: 192.168.56.110

[root@k8s-master01 ~]# kubectl create -f pv-nfs.yml

persistentvolume/pv0001 created

[root@k8s-master01 ~]# kubectl get pv

NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE

pv0001 5Gi RWX Recycle

创建pvc ：

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: myclaim
spec:
  accessModes:
    - ReadWriteMany
  volumeMode: Filesystem
  resources:
    requests:
      storage: 5Gi
  storageClassName: nfs-slow

新建一个pod, 挂载上面的pvc:

apiVersion: v1
kind: Pod
metadata:
  name: my-pv-pod
spec:
  containers:
    - name: myfrontend
      image: nginx:1.14.2
      volumeMounts:
      - mountPath: "/var/www/html"
        name: my-nginx
  volumes:
    - name: my-nginx
      persistentVolumeClaim:
        claimName: myclaim

补充：若要删除 pvc 需要先剔除对该pvc 的引用。否则删除会卡住。然后重新启动pod 或者deployment 时，会出现pending 状态。

!$ 把上一条命令的参数作为标准输入
!! 运行最近一次执行的命令
$0 这个程式的执行名字
$n 这个程式的第n个参数值，n=1…9，超过10个加一对花括号把参数引起来 eg. ${11}。
$* 这个程式的所有参数,此选项参数可超过9个。
$# 这个程式的参数个数
$$ 这个程式的PID(脚本运行的当前进程ID号)
$! 执行上一个背景指令的PID(后台运行的最后一个进程的进程ID号)
$? 执行上一个指令的返回值 (显示最后命令的退出状态。0表示没有错误，其他任何值表明有错误)
$- 显示shell使用的当前选项，与set命令功能相同