k8s使用nfs做storageclass

本文提供了一套完整的Kubernetes环境中部署NFS-Provisioner的方法,包括镜像下载、权限配置、部署文件及StorageClass的创建等关键步骤。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

镜像下载与私仓上传
docker pull docker.io/lhcre/nfs-client-provisioner
docker tag docker.io/lhcre/nfs-client-provisioner 172.16.15.250/nfs-client-provisioner
docker push 172.16.15.250/nfs-client-provisioner
权限控制 nfs-rbac.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: nfs-client-provisioner-one
  namespace: default
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: nfs-client-provisioner-one-runner
rules:
  - 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-one
subjects:
  - kind: ServiceAccount
    name: nfs-client-provisioner-one
    namespace: default
roleRef:
  kind: ClusterRole
  name: nfs-client-provisioner-one-runner
  apiGroup: rbac.authorization.k8s.io
---
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: leader-locking-nfs-client-provisioner-one
  # 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-one
  # replace with namespace where provisioner is deployed
  namespace: defaultl
subjects:
  - kind: ServiceAccount
    name: nfs-client-provisioner-one
    # replace with namespace where provisioner is deployed
    namespace: default
roleRef:
  kind: Role
  name: leader-locking-nfs-client-provisioner-one
  apiGroup: rbac.authorization.k8s.io

如果不想将nfs-provisioner部署在default,则执行下面操作(假设部署在nfs)

[root@master1 nfs]# kubectl create ns nfs
[root@master1 nfs]# sed -i 's/namespace: default/namespace: nfs/g' nfs-rbac.yml
[root@master1 nfs]# kubectl apply -f nfs-rbac.yml -n nfs
nfs-provisioner部署文件 nfs-provisioner.yaml

!!!配置nfs服务器地址和共享的出来的路径

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nfs-client-provisioner-one
  labels:
    app: nfs-client-provisioner-one
spec:
  replicas: 1
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app: nfs-client-provisioner-one
  template:
    metadata:
      labels:
        app: nfs-client-provisioner-one
    spec:
      serviceAccountName: nfs-client-provisioner-one
      containers:
        - name: nfs-client-provisioner-one
          #!!!修改值---镜像
          image: 172.16.15.250/nfs-client-provisioner
          volumeMounts:
            - name: nfs-client-root
              mountPath: /persistentvolumes
          env:
            - name: PROVISIONER_NAME
              #!!!修改值---后续创建storageclass时需要用到该参数
              value: nfsone
            - name: NFS_SERVER
              #!!!修改值---nfs服务器地址
              value: 172.16.15.121
            - name: NFS_PATH
              #!!!修改值---nfs共享出来的路径
              value: /data-nfs
      volumes:
        - name: nfs-client-root
          nfs:
            #!!!修改值---nfs服务器地址
            server: 172.16.15.121
            #!!!修改值---nfs共享出来的路径
            path: /data-nfs

部署

kubectl apply -f nfs-provisioner.yaml -n nfs
部署storageclass—nfs-storageclass.yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  #创建PVC时会用到的参数
  name: nfs-one
  labels:
    uds.dce.daocloud.io/storage-type: file
  annotations:
   # 设置该storageclass为PVC创建时默认使用的存储机制;如果不设置该参数,PVC想要使用该storageclass时需要指定 storageclassname
    storageclass.kubernetes.io/is-default-class: "true" 
#!!!修改值---匹配deployment中的环境变量'PROVISIONER_NAME'
provisioner: nfsone
parameters:
  archiveOnDelete: "true" # "false" 删除PVC时不会保留数据,"true"将保留PVC数据
reclaimPolicy: Retain

部署

kubectl apply -f nfs-storageclass.yaml -n nfs
pvc使用该storageclass
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: hello-pvc
spec:
  storageClassName: nfs-one
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
5、查看是否绑定
kubectl get pvc 
<think>嗯,用户想了解在Kubernetes中安装NFS存储驱动并创建NFSStorageClass。我需要一步步解释清楚,确保他们能正确操作。首先,应该确认他们已经有NFS服务器和可用的共享目录,这点很重要,因为后续步骤都依赖这个前提。 接下来,可能需要安装NFS的客户端工具,比如nfs-common,这在每个节点上都需要。用户可能不知道这点,所以得提醒他们检查所有节点是否已安装。 然后,部署NFS的Provisioner。这里有两个选择,用Deployment或者StatefulSet。通常Deployment更常见,但要根据实际需求。需要提供NFS服务器的地址和路径,这里得用变量让用户替换成自己的信息。同时,要提到RBAC的配置,包括ServiceAccount、Role和RoleBinding,否则权限可能不够。 创建StorageClass的时候,要指定provisioner的名称,确保和Provisioner的配置一致。用户可能需要调整回收策略,比如Retain还是Delete,这里需要说明两者的区别,避免数据丢失。 测试部分,创建PVC和示例应用来验证存储是否正常。用户可能遇到PVC一直处于Pending状态,这时候需要检查Provisioner的日志,还有NFS的共享权限是否正确。此外,Provisioner的镜像版本也要注意,避免兼容性问题。 最后,总结整个流程,并提醒常见问题,比如网络连通性、权限设置和资源限制。用户可能需要这些信息来排查问题。整个过程要结构清晰,步骤明确,避免遗漏关键点。同时,使用中文,保持自然,不用专业术语过多,让新手也能理解。</think>好的,我来分步骤解释如何在Kubernetes中创建NFS StorageClass: ----- ### 第一步:准备NFS服务器 1. 确保已有NFS服务器(假设IP为192.168.1.100) 2. 创建共享目录(示例:/data/nfs) 3. 配置exports文件: ```bash # /etc/exports /data/nfs *(rw,sync,no_root_squash) ``` ### 第二步:安装NFS客户端工具 在所有Kubernetes节点执行: ```bash sudo apt-get install -y nfs-common # Ubuntu/Debian sudo yum install -y nfs-utils # CentOS/RHEL ``` ### 第三步:部署NFS Provisioner 创建nfs-provisioner.yaml: ```yaml # 创建ServiceAccount和RBAC apiVersion: v1 kind: ServiceAccount metadata: name: nfs-provisioner --- kind: ClusterRole apiVersion: rbac.authorization.k8s.io/v1 metadata: name: nfs-provisioner-runner rules: - apiGroups: [""] resources: ["persistentvolumes"] verbs: ["get", "list", "watch", "create", "delete"] - apiGroups: [""] resources: ["persistentvolumeclaims"] verbs: ["get", "list", "watch", "update"] --- kind: ClusterRoleBinding apiVersion: rbac.authorization.k8s.io/v1 metadata: name: run-nfs-provisioner subjects: - kind: ServiceAccount name: nfs-provisioner namespace: default roleRef: kind: ClusterRole name: nfs-provisioner-runner apiGroup: rbac.authorization.k8s.io # 部署Provisioner(使用Deployment) apiVersion: apps/v1 kind: Deployment metadata: name: nfs-provisioner spec: replicas: 1 selector: matchLabels: app: nfs-provisioner template: metadata: labels: app: nfs-provisioner spec: serviceAccount: nfs-provisioner containers: - name: nfs-provisioner image: k8s.gcr.io/sig-storage/nfs-subdir-external-provisioner:v4.0.2 env: - name: NFS_SERVER value: 192.168.1.100 - name: NFS_PATH value: /data/nfs volumeMounts: - name: nfs-client-root mountPath: /persistentvolumes volumes: - name: nfs-client-root nfs: server: 192.168.1.100 path: /data/nfs ``` ### 第四步:创建StorageClass 创建storageclass.yaml: ```yaml apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: nfs-storage provisioner: cluster.local/nfs-provisioner parameters: archiveOnDelete: "false" # 删除时是否保留数据 reclaimPolicy: Retain # 回收策略(Retain/Delete) ``` ### 第五步:应用配置 ```bash kubectl apply -f nfs-provisioner.yaml kubectl apply -f storageclass.yaml ``` ### 第六步:验证测试 1. 创建测试PVC: ```yaml apiVersion: v1 kind: PersistentVolumeClaim metadata: name: test-pvc spec: storageClassName: nfs-storage accessModes: - ReadWriteMany resources: requests: storage: 1Gi ``` 2. 部署测试Pod: ```yaml apiVersion: v1 kind: Pod metadata: name: test-pod spec: containers: - name: test-container image: busybox command: ["/bin/sh", "-c", "sleep 3600"] volumeMounts: - name: test-volume mountPath: /mnt volumes: - name: test-volume persistentVolumeClaim: claimName: test-pvc ``` ----- ### 常见问题排查 1. **PVC处于Pending状态**: - 检查Provisioner日志:`kubectl logs -l app=nfs-provisioner` - 确认NFS共享目录权限 - 检查网络连通性(node到NFS服务器的2049端口) 2. **删除资源后数据保留**: 根据`reclaimPolicy`参数: - `Retain`:手动清理PV和数据 - `Delete`:自动删除PV和NFS目录 3. **性能优化建议**: ```yaml parameters: mountOptions: "noatime,nodiratime,vers=4.1" # 使用NFSv4协议 ``` ### 版本说明 - 推荐使用较新的nfs-subdir-external-provisioner(v4.0+) - Kubernetes版本建议v1.20+ 这个方案适合中小规模集群,如需高可用可部署多个Provisioner实例并配置反亲和性。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值