当前位置：网站首页>PV静态创建和动态创建
PV静态创建和动态创建
2022-07-05 23:32:00 【江小南】
NFS（Network File System）
在使用Kubernetes的过程中，我们经常会用到存储。存储的最大作用，就是使容器内的数据实现持久化保存，防止删库跑路的现象发生。而要实现这一功能，就离不开网络文件系统。kubernetes通过NFS网络文件系统，将每个节点的挂载数据进行同步，那么就保证了pod被故障转移等情况，依然能读取到被存储的数据。
一、安装NFS
在kubernetes集群内安装NFS。
所有节点执行
yum install -y nfs-utils
nfs主节点执行
echo "/nfs/data/ *(insecure,rw,sync,no_root_squash)" > /etc/exports # 暴露了目录/nfs/data/，`*`表示所有节点都可以访问。
mkdir -p /nfs/data
systemctl enable rpcbind --now
systemctl enable nfs-server --now
# 配置生效
exportfs -r
# 检查验证
[[email protected] ~]# exportfs
/nfs/data <world>
[[email protected] ~]#
nfs从节点执行
# 展示172.31.0.2有哪些目录可以挂载
showmount -e 172.31.0.2 # ip改成自己的主节点ip
mkdir -p /nfs/data
# 将本地目录和远程目录进行挂载
mount -t nfs 172.31.0.2:/nfs/data /nfs/data
二、验证
# 写入一个测试文件
echo "hello nfs server" > /nfs/data/test.txt
通过这些步骤，我们可以看到NFS文件系统已经安装成功。172.31.0.2作为系统的主节点，暴露了/nfs/data，其他从节点的/nfs/data和主节点的/nfs/data进行了挂载。在kubernetes集群内，可以任意选取一台服务器作为server，其他服务器作为client。
PV&PVC
PV：持久卷（Persistent Volume），将应用需要持久化的数据保存到指定位置。
PVC：持久卷申明（Persistent Volume Claim），申明需要使用的持久卷规格。
Pod中的数据需要持久化保存，保存到哪里呢?当然是保存到PV中，PV所在的位置，就是我们上面说到的NFS文件系统。那么如何使用PV呢？就是通过PVC。就好比PV是存储，PVC就是告诉PV，我要开始使用你了。
PV的创建一般分为两种，静态创建和动态创建。静态创建就是提前创建好很多PV，形成一个PV池，按照PVC的规格要求选择合适的进行供应。动态创建则不事先创建，而是根据PVC的规格要求，要求什么规格的就创建什么规格的。从资源的利用角度来讲，动态创建要更好一些。
一、静态创建PV
创建数据存放目录。
# nfs主节点执行
[[email protected] data]# pwd
/nfs/data
[[email protected] data]# mkdir -p /nfs/data/01
[[email protected] data]# mkdir -p /nfs/data/02
[[email protected] data]# mkdir -p /nfs/data/03
[[email protected] data]# ls
01 02 03
[[email protected] data]#
创建PV，pv.yml
apiVersion: v1
kind: PersistentVolume
metadata:
name: pv01-10m
spec:
capacity:
storage: 10M
accessModes:
- ReadWriteMany
storageClassName: nfs
nfs:
path: /nfs/data/01
server: 172.31.0.2
---
apiVersion: v1
kind: PersistentVolume
metadata:
name: pv02-1gi
spec:
capacity:
storage: 1Gi
accessModes:
- ReadWriteMany
storageClassName: nfs
nfs:
path: /nfs/data/02
server: 172.31.0.2
---
apiVersion: v1
kind: PersistentVolume
metadata:
name: pv03-3gi
spec:
capacity:
storage: 3Gi
accessModes:
- ReadWriteMany
storageClassName: nfs
nfs:
path: /nfs/data/03
server: 172.31.0.2
[[email protected] ~]# kubectl apply -f pv.yml
persistentvolume/pv01-10m created
persistentvolume/pv02-1gi created
persistentvolume/pv03-3gi created
[[email protected] ~]# kubectl get persistentvolume
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
pv01-10m 10M RWX Retain Available nfs 45s
pv02-1gi 1Gi RWX Retain Available nfs 45s
pv03-3gi 3Gi RWX Retain Available nfs 45s
[[email protected] ~]#
三个文件夹对应三个PV，大小分别为10M、1Gi、3Gi，这三个PV形成一个PV池。
创建PVC，pvc.yml
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: nginx-pvc
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 200Mi
storageClassName: nfs
[[email protected] ~]# kubectl apply -f pvc.yml
persistentvolumeclaim/nginx-pvc created
[[email protected] ~]# kubectl get pvc,pv
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
persistentvolumeclaim/nginx-pvc Bound pv02-1gi 1Gi RWX nfs 14m
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
persistentvolume/pv01-10m 10M RWX Retain Available nfs 17m
persistentvolume/pv02-1gi 1Gi RWX Retain Bound default/nginx-pvc nfs 17m
persistentvolume/pv03-3gi 3Gi RWX Retain Available nfs 17m
[[email protected] ~]#
可以发现使用200Mi的PVC，会在PV池中绑定最佳的1Gi大小的pv02-1gi的PV去使用，状态为Bound。后面创建Pod或Deployment的时候，使用PVC即可将数据持久化保存到PV中，而且NFS的任意节点可以同步。
二、动态创建PV
配置动态供应的默认存储类，sc.yml
# 创建了一个存储类
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: nfs-storage
annotations:
storageclass.kubernetes.io/is-default-class: "true"
provisioner: k8s-sigs.io/nfs-subdir-external-provisioner
parameters:
archiveOnDelete: "true" ## 删除pv的时候，pv的内容是否要备份
---
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: registry.cn-hangzhou.aliyuncs.com/lfy_k8s_images/nfs-subdir-external-provisioner:v4.0.2
# resources:
# limits:
# cpu: 10m
# requests:
# cpu: 10m
volumeMounts:
- name: nfs-client-root
mountPath: /persistentvolumes
env:
- name: PROVISIONER_NAME
value: k8s-sigs.io/nfs-subdir-external-provisioner
- name: NFS_SERVER
value: 172.31.0.2 ## 指定自己nfs服务器地址
- name: NFS_PATH
value: /nfs/data ## nfs服务器共享的目录
volumes:
- name: nfs-client-root
nfs:
server: 172.31.0.2
path: /nfs/data
---
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
这里注意ip修改为自己的，而且镜像仓库地址已换成阿里云的，防止镜像下载不下来。
[[email protected] ~]# kubectl apply -f sc.yml
storageclass.storage.k8s.io/nfs-storage created
deployment.apps/nfs-client-provisioner created
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
[[email protected] ~]#
确认配置是否生效
[[email protected] ~]# kubectl get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
nfs-storage (default) k8s-sigs.io/nfs-subdir-external-provisioner Delete Immediate false 6s
[[email protected] ~]#
动态供应测试，pvc.yml
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: nginx-pvc
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 200Mi
[[email protected] ~]# kubectl apply -f pvc.yml
persistentvolumeclaim/nginx-pvc created
[[email protected] ~]# kubectl get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
nginx-pvc Bound pvc-7b01bc33-826d-41d0-a990-8c1e7c997e6f 200Mi RWX nfs-storage 9s
[[email protected] ~]# kubectl get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-7b01bc33-826d-41d0-a990-8c1e7c997e6f 200Mi RWX Delete Bound default/nginx-pvc nfs-storage 16s
[[email protected] ~]#
pvc声明需要200Mi的空间，那么便创建了200Mi的pv，状态为Bound，测试成功。后面创建Pod或Deployment的时候，使用PVC即可将数据持久化保存到PV中，而且NFS的任意节点可以同步。
小结
这样就能明白了，NFS、PV和PVC为kubernetes集群提供了数据存储支持，应用被任意节点部署，那么之前的数据依然能够读取到。
边栏推荐
- TVS管 与 稳压二极管参数对比
- How to improve eloquence
- Spire Office 7.5.4 for NET
- GFS distributed file system
- Use mapper: --- tkmapper
- Bao Yan notes II software engineering and calculation volume II (Chapter 13-16)
- LeetCode——Add Binary
- 11gR2 Database Services for ＆quot; Policy＆quot; and ＆quot; Administrator＆quot; Managed databases (file I
- UVA11294-Wedding(2-SAT)
- Hcip course notes-16 VLAN, three-tier architecture, MPLS virtual private line configuration
猜你喜欢
698. 划分为k个相等的子集 ●●
Initial experience | purchase and activate typora software
20220703 周赛：知道秘密的人数-动规（题解）
Huawei simulator ENSP - hcip - MPLS experiment
GFS分布式文件系统
Live tiktok shop 2022 latest gameplay card slot overseas live e-commerce new traffic
orgchart. JS organization chart, presenting structural data in an elegant way
Spécifications techniques et lignes directrices pour la sélection des tubes TVS et ESD - Recommandation de jialichuang
Redis高可用——主从复制、哨兵模式、集群
4 points tell you the advantages of the combination of real-time chat and chat robots
随机推荐
It is proved that POJ 1014 module is optimized and pruned, and some recursion is wrong
Neural structured learning 4 antagonistic learning for image classification
CIS benchmark tool Kube bench
[classical control theory] summary of automatic control experiment
Idea connects to MySQL, and it is convenient to paste the URL of the configuration file directly
MySQL replace primary key delete primary key add primary key
Dynamic planning: robbing families and houses
Spire.PDF for NET 8.7.2
Neural structured learning - Part 2: training with natural graphs
C＃ 反射与Type
[original] what is the core of programmer team management?
Live tiktok shop 2022 latest gameplay card slot overseas live e-commerce new traffic
无刷驱动设计——浅谈MOS驱动电路
Brushless drive design -- on MOS drive circuit
98. 验证二叉搜索树 ●●
Latex multiple linebreaks
Use mapper: --- tkmapper
PADS ROUTER 使用技巧小记
98. Verify the binary search tree ●●
UVA – 11637 Garbage Remembering Exam （组合+可能性）