Kubernetes使用StorageClass动态生成NFS类型的PV

网友投稿 303 2022-09-10

Kubernetes使用StorageClass动态生成NFS类型的PV

什么是StorageClass

StorageClass对象会定义下面两部分内容:

1: PV的属性.比如,存储类型,Volume的大小等2: 创建这种PV需要用到的存储插件

但是其实使用起来是一件很简单的事情,你只需要根据自己的需求,编写YAML文件即可,然后使用​​kubectl create​​命令执行即可。

流程

创建一个可用的 NFS Serve创建 Service Account. 这是用来管控 NFS provisioner 在k8s集群中运行的权限创建 StorageClass. 负责建立PVC并调用 NFS provisioner 进行预定的工作, 并让 PV 与 PVC 建立管理创建 NFS provisioner. 有两个功能,一个是在 NFS 共享目录下创建挂载点(volume), 另一个则是建了 PV 并将 PV 与 NFS 的挂载点建立关联

server

ip

comment

kubernetes-master

172.20.5.10

master

kubernetes-node1

172.20.5.11

node1

kubernetes-node2

172.20.5.12

node2

nfs-server

172.20.2.10

NFS

创建StorageClass

创建NFS共享服务

[root@nfs nfsdata]# yum install -y nfs-utils[root@nfs nfsdata]# mkdir /nfsdata[root@nfs nfsdata]# chmod 755 /nfsdata[root@nfs nfsdata]# chown nfsnobody:nfsnobody /nfsdata/[root@nfs nfsdata]# echo "/nfsdata *(rw,sync,all_squash)" > /etc/exports[root@nfs nfsdata]# systemctl enable nfs[root@nfs nfsdata]# systemctl start nfs[root@nfs nfsdata]# exportfs -rvexporting *:/nfsdata复制代码

创建account及相关权限

nfs-rbac.yaml

apiVersion: v1kind: ServiceAccountmetadata: name: nfs-provisioner namespace: nfs-provisioner---kind: ClusterRoleapiVersion: rbac.authorization.k8s.io/v1metadata: name: nfs-provisioner-runnerrules:- 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: ClusterRoleBindingapiVersion: rbac.authorization.k8s.io/v1metadata: name: run-nfs-provisionersubjects:- kind: ServiceAccount name: nfs-provisioner # replace with namespace where provisioner is deployed namespace: nfs-provisionerroleRef: kind: ClusterRole name: nfs-provisioner-runner apiGroup: rbac.authorization.k8s.io---kind: RoleapiVersion: rbac.authorization.k8s.io/v1metadata: name: leader-locking-nfs-provisioner # replace with namespace where provisioner is deployed namespace: nfs-provisionerrules:- apiGroups: [""] resources: ["endpoints"] verbs: ["get", "list", "watch", "create", "update", "patch"]---kind: RoleBindingapiVersion: rbac.authorization.k8s.io/v1metadata: name: leader-locking-nfs-provisionersubjects:- kind: ServiceAccount name: nfs-provisioner # replace with namespace where provisioner is deployed namespace: nfs-provisionerroleRef: kind: Role name: leader-locking-nfs-provisioner apiGroup: rbac.authorization.k8s.io复制代码

创建NFS资源的StorageClass

nfs-storageclass.yaml

kind: StorageClassapiVersion: storage.k8s.io/v1metadata: name: nfsprovisioner: example.com/nfs #这里的名称要和provisioner配置文件中的环境变量PROVISIONER_NAME保持一致复制代码

创建NFS provisioner Deployment

nfs-deployment.yaml

kind: DeploymentapiVersion: apps/v1metadata: name: nfs-provisioner namespace: nfs-provisionerspec: replicas: 1 selector: matchLabels: app: nfs-provisioner strategy: type: Recreate template: metadata: labels: app: nfs-provisioner spec: serviceAccount: nfs-provisioner containers: - name: nfs-provisioner image: registry.cn-hangzhou.aliyuncs.com/open-ali/nfs-client-provisioner volumeMounts: - name: nfs-client-root mountPath: /persistentvolumes env: - name: PROVISIONER_NAME value: example.com/nfs - name: NFS_SERVER value: 172.20.2.10 - name: NFS_PATH value: /nfsdata volumes: - name: nfs-client-root nfs: server: 172.20.2.10 path: /nfsdata复制代码

[root@kubernetes-master nfs]# lltotal 20-rw-r--r-- 1 root root 894 Dec 9 13:55 nfs-deployment.yaml-rw-r--r-- 1 root root 65 Dec 9 14:50 nfs-namespace.yaml-rw-r--r-- 1 root root 1449 Dec 9 15:15 nfs-rbac.yaml-rw-r--r-- 1 root root 100 Dec 9 14:18 nfs-storageclass.yaml复制代码

创建Pod,检测部署

pvc-nfs.yaml

apiVersion: v1kind: PersistentVolumeClaimmetadata: name: pvc-nfsspec: accessModes: - ReadWriteOnce storageClassName: nfs resources: requests: storage: 1Gi复制代码

[root@kubernetes-master nfs]# kubectl apply -f pvc-nfs.yaml persistentvolumeclaim/pvc-nfs created[root@kubernetes-master nfs]# kubectl get pvcNAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGEpvc-nfs Bound pvc-7461b40b-f52e-4bf6-9d73-40432b77f108 1Gi RWO nfs 1s复制代码

创建测试pod,查看是否可以正常挂载

kind: PodapiVersion: v1metadata: name: test-podspec: containers: - name: test-pod image: busybox:1.24 command: - "/bin/sh" args: - "-c" - "touch /mnt/SUCCESS && exit 0 || exit 1" #创建一个SUCCESS文件后退出 volumeMounts: - name: pvc-nfs mountPath: "/mnt" restartPolicy: "Never" volumes: - name: pvc-nfs persistentVolumeClaim: claimName: pvc-nfs #与PVC名称保持一致复制代码

[root@nfs nfsdata]# ll default-pvc-nfs-pvc-7461b40b-f52e-4bf6-9d73-40432b77f108/total 0-rw-r--r-- 1 nfsnobody nfsnobody 0 Dec 9 15:29 SUCCESS #下面有一个 SUCCESS 的文件,证明我们上面的验证是成功

版权声明:本文内容由网络用户投稿,版权归原作者所有,本站不拥有其著作权,亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容,请联系我们jiasou666@gmail.com 处理,核实后本网站将在24小时内删除侵权内容。

上一篇:未来营销主宰:不是广告人而是技术宅?
下一篇:k8s学习-部署应用实例1
相关文章

 发表评论

暂时没有评论,来抢沙发吧~