版权声明：知识就是为了传播！ https://blog.csdn.net/weixin_36171533/article/details/82627920
下面做一个基于NFS的存储
NFS支持多客户端的读写
新建立一个主机
node3：192.168.68.30
安装
yum -y install nfs-utils
建立共享文件夹：
mkdir /data/volumes -pv
设置共享：
vim /etc/exports
/data/volumes 172.20.0.0/16(rw,no_root_squash)
目录 授权给 网段 权限
注意172.20.0.0是node的网段
启动NFS
systemctl start nfs
查看2049端口是否打开
ss -tnl
在node1和node2也安装nfs
yum install nfs-utils -y
确保每个节点暗账nfs
在node2上测试挂载成功
[root@node2 ~]# mount -t nfs node3:/data/volumes /mnt
mount.nfs: access denied by server while mounting node3:/data/volumes #这是挂载失败
测试命令：mount 一定看看最下面有没有挂载的命令，有则是挂载成功的
node3:/data/volumes on /mnt type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.68.20,local_lock=none,addr=192.168.68.40)
取消挂载：
umount /mnt[root@master volumes]# cat pod-vol-nfs.yaml
apiVersion: v1
kind: Pod
metadata:
name: pod-vol-nfs
namespace: default
spec:
containers:
- name: myapp
image: ikubernetes/myapp:v1
volumeMounts:
- name: html
mountPath: /usr/share/nginx/html/
volumes:
- name: html
nfs:
path: /data/volumes
server: node3.com
创建 kubectl apply -f pod-vol-nfs.yaml
[root@node3 volumes]# cd /data/volumes/
[root@node3 volumes]# vim index.html 输入：hello，word查看kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE
pod-vol-nfs 1/1 Running 0 12s 10.244.2.56 node2 <none>
[root@master volumes]# curl 10.244.2.56
hello,word思考：这是一种利用NFS方式挂载到k8S内部的方式，有点，pod挂掉后数据还在，适合做存储。
前提是每个节点都安装NFS
#####################################################
开始做PV和PVC实验
vim /etc/exports
/data/volumes/v1 192.168.0.0/16(rw,no_root_squash)
/data/volumes/v2 192.168.0.0/16(rw,no_root_squash)
/data/volumes/v3 192.168.0.0/16(rw,no_root_squash)
/data/volumes/v4 192.168.0.0/16(rw,no_root_squash)
/data/volumes/v5 192.168.0.0/16(rw,no_root_squash)
重新加载配置：
[root@node3 volumes]# exportfs -arv
exporting 192.168.0.0/16:/data/volumes/v5
exporting 192.168.0.0/16:/data/volumes/v4
exporting 192.168.0.0/16:/data/volumes/v3
exporting 192.168.0.0/16:/data/volumes/v2
exporting 192.168.0.0/16:/data/volumes/v1
[root@node3 volumes]# showmount -e
Export list for node3:
/data/volumes/v5 192.168.0.0/16
/data/volumes/v4 192.168.0.0/16
/data/volumes/v3 192.168.0.0/16
/data/volumes/v2 192.168.0.0/16
/data/volumes/v1 192.168.0.0/16
查看PV的帮助文档
kuebctl explain pv
kubectl explain pv.spec.nfs创建yaml文件
[root@master volumes]# cat pvs-demo.yaml
apiVersion: v1
kind: PersistentVolume
metadata:
name: pv001
labels:
name: pv001
spec:
nfs:
path: /data/volumes/v1
server: node3
accessModes: ["ReadWriteMany","ReadWriteOnce"]
capacity:
storage: 5Gi
---
apiVersion: v1
kind: PersistentVolume
metadata:
name: pv002
labels:
name: pv002
spec:
nfs:
path: /data/volumes/v2
server: node3
accessModes: ["ReadWriteMany","ReadWriteOnce"]
capacity:
storage: 7Gi
---
apiVersion: v1
kind: PersistentVolume
metadata:
name: pv003
labels:
name: pv003
spec:
nfs:
path: /data/volumes/v1
server: node3
accessModes: ["ReadWriteMany","ReadWriteOnce"]
capacity:
storage: 8Gi
---
apiVersion: v1
kind: PersistentVolume
metadata:
name: pv004
labels:
name: pv004
spec:
nfs:
path: /data/volumes/v4
server: node3
accessModes: ["ReadWriteMany","ReadWriteOnce"]
capacity:
storage: 10Gi
---
apiVersion: v1
kind: PersistentVolume
metadata:
name: pv005
labels:
name: pv005
spec:
nfs:
path: /data/volumes/v5
server: node3
accessModes: ["ReadWriteMany","ReadWriteOnce"]
capacity:
storage: 12Gi
--- 开始创建：
[root@master volumes]# kubectl get pv
No resources found.
[root@master volumes]# kubectl apply -f pvs-demo.yaml
persistentvolume/pv001 created
persistentvolume/pv002 created
persistentvolume/pv003 created
persistentvolume/pv004 created
persistentvolume/pv005 created
[root@master volumes]# kubectl get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
pv001 5Gi RWO,RWX Retain Available 7s
pv002 7Gi RWO,RWX Retain Available 7s
pv003 8Gi RWO,RWX Retain Available 7s
pv004 10Gi RWO,RWX Retain Available 7s
pv005 12Gi RWO,RWX Retain Available 7s
[root@master volumes]# pv定义完成，我们定义pvc
[root@master volumes]# cat pod-vol-pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: mypvc
namespace: default
spec:
accessModes: ["ReadWriteMany"]
resources:
requests:
storage: 6Gi #定义的资源是6G，他会在资源中自动寻找合适的
---
apiVersion: v1
kind: Pod
metadata:
name: pod-vol-nfs
namespace: default
spec:
containers:
- name: myapp
image: ikubernetes/myapp:v1
volumeMounts:
- name: html
mountPath: /usr/share/nginx/html/
volumes:
- name: html
persistentVolumeClaim:
claimName: mypvc
创建资源
[root@master volumes]# kubectl apply -f pod-vol-pvc.yaml
persistentvolumeclaim/mypvc created
pod/pod-vol-nfs created
[root@master volumes]# kubectl get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
pv001 5Gi RWO,RWX Retain Available 16m
pv002 7Gi RWO,RWX Retain Bound default/mypvc 16m #自动寻找到PV002上
pv003 8Gi RWO,RWX Retain Available 16m
pv004 10Gi RWO,RWX Retain Available 16m
pv005 12Gi RWO,RWX Retain Available 16m我们查看一下PVC的状态
[root@master volumes]# kubectl get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
mypvc Bound pv002 7Gi RWO,RWX 3m