如果你想在 Kubernetes 中使用 NFS 存储,可以按照以下步骤创建存储类和 PVC:

1、创建rbac.yaml 文件

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
apiVersion: v1
kind: ServiceAccount
metadata:
name: nfs-client-provisioner
# replace with namespace where provisioner is deployed
namespace: default #根据实际环境设定namespace,下面类同
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: nfs-client-provisioner-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
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
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

  • 根据实际环境设定namespace。

2、创建nfs-provisioner.yaml 文件

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
apiVersion: apps/v1
kind: Deployment
metadata:
name: nfs-client-provisioner
labels:
app: nfs-client-provisioner
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: gcr.io/k8s-staging-sig-storage/nfs-subdir-external-provisioner:v4.0.0
volumeMounts:
- name: nfs-client-root
mountPath: /persistentvolumes
env:
- name: PROVISIONER_NAME
value: default-nfs-storage
- name: NFS_SERVER
value: 192.168.10.14
- name: NFS_PATH
value: /export
volumes:
- name: nfs-client-root
nfs:
server: 192.168.10.14
path: /export

  • PROVISIONER_NAME的值要和nfs-storage-class.yaml中provisioner一致
  • NFS_SERVER:nfs服务的IP,更换成你自己的IP
  • NFS_PATH:nfs共享的路径,更换成你自己的

3、创建nfs-pvc.yaml 文件

1
2
3
4
5
6
7
8
9
10
11
12
13
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: nfs-pvc
annotations:
volume.beta.kubernetes.io/storage-class: "managed-nfs-storage"
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 5Gi

  • metadata.annotations.volume.beta.kubernetes.io/storage-class的值要和nfs-storage-class.yaml中的metadata.name一致

4、创建nfs-storage-class.yaml 文件

1
2
3
4
5
6
7
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: managed-nfs-storage
provisioner: default-nfs-storage
parameters:
archiveOnDelete: "false"

5、执行

1
2
3
4
sudo kubectl apply -f rbac.yaml
sudo kubectl apply -f nfs-pvc.yaml
sudo kubectl apply -f nfs-provisioner.yaml
sudo kubectl apply -f nfs-storage-class.yaml

6、查看结果

1
2
3
4
5
6
7
8
9
10
11
12
13
14
diky@ubuntu:/opt/components$ sudo kubectl get pv,pvc,sc,pod
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
persistentvolume/pvc-495ff088-59ff-4bdb-8c46-1ba65800eace 5Gi RWX Delete Bound default/nfs-pvc managed-nfs-storage 62m

NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
persistentvolumeclaim/nfs-pvc Bound pvc-495ff088-59ff-4bdb-8c46-1ba65800eace 5Gi RWX managed-nfs-storage 23h

NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
storageclass.storage.k8s.io/local-path (default) rancher.io/local-path Delete WaitForFirstConsumer false 47h
storageclass.storage.k8s.io/managed-nfs-storage default-nfs-storage Delete Immediate false 25h

NAME READY STATUS RESTARTS AGE
pod/nfs-client-provisioner-7f596764c4-zc8kk 1/1 Running 1 (61m ago) 64m

  • 如果pvc的STATUS为Bound就说明已经部署好了