microk8s部署nfs存储
2023-09-06 本文已影响0人
hewolf
参考官方文档
https://microk8s.io/docs/how-to-nfs
https://github.com/kubernetes-csi/csi-driver-nfs/blob/master/docs/install-csi-driver-v4.4.0.md
1.设置nfs服务器
# 安装服务
sudo apt-get install nfs-kernel-server
# 创建用于NFS的目录：
sudo mkdir -p /srv/nfs
sudo chown nobody:nogroup /srv/nfs
sudo chmod 0777 /srv/nfs
# 编辑 /etc/exports 文件。确保所有MicroK8s节点的IP地址都能够装载此共享。例如，要允许 10.0.0.0/24 子网中的所有IP地址：
sudo mv /etc/exports /etc/exports.bak
echo '/srv/nfs 10.0.0.0/24(rw,sync,no_subtree_check)' | sudo tee /etc/exports
# 不确定ip限制可以用
# 最后，重新启动NFS服务器：/srv/nfs *(rw,sync,no_subtree_check)
sudo systemctl restart nfs-kernel-server
2.安装NFS的CSI驱动程序
git clone git@github.com:kubernetes-csi/csi-driver-nfs.git
cd csi-driver-nfs/deploy/v4.1.0
kubectl apply -f rbac-csi-nfs.yaml -f csi-nfs-driverinfo.yaml -f csi-nfs-controller.yaml -f csi-nfs-node.yaml
## 检查节点是否正常
kubectl -n kube-system get pod -o wide -l app=csi-nfs-controller
kubectl -n kube-system get pod -o wide -l app=csi-nfs-node
# 解决镜像拉取问题
microk8s ctr image pull registry.aliyuncs.com/google_containers/csi-node-driver-registrar:v2.5.1
microk8s ctr image tag registry.aliyuncs.com/google_containers/csi-node-driver-registrar:v2.5.1 registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.5.1
microk8s ctr image pull registry.aliyuncs.com/google_containers/livenessprobe:v2.7.0
microk8s ctr image tag registry.aliyuncs.com/google_containers/livenessprobe:v2.7.0 registry.k8s.io/sig-storage/livenessprobe:v2.7.0
microk8s ctr image pull lank8s.cn/sig-storage/nfsplugin:v4.1.0
microk8s ctr image tag lank8s.cn/sig-storage/nfsplugin:v4.1.0 registry.k8s.io/sig-storage/nfsplugin:v4.1.0
microk8s ctr image pull lank8s.cn/sig-storage/csi-provisioner:v3.2.0
microk8s ctr image tag lank8s.cn/sig-storage/csi-provisioner:v3.2.0 registry.k8s.io/sig-storage/csi-provisioner:v3.2.0
microk8s ctr image pull lank8s.cn/sig-storage/csi-snapshotter:v6.2.2
microk8s ctr image tag lank8s.cn/sig-storage/csi-snapshotter:v6.2.2 registry.k8s.io/sig-storage/csi-snapshotter:v6.2.2
# 成功后显示如下
root@ubuntu02:/home/k8s/csi-driver-nfs/deploy/v4.4.0# kubectl -n kube-system get pod -o wide -l app=csi-nfs-controller
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
csi-nfs-controller-6f5f9cb8f-fw7pw 4/4 Running 0 3m54s 192.168.1.9 ubuntu04 <none> <none>
root@ubuntu02:/home/k8s/csi-driver-nfs/deploy/v4.4.0# kubectl -n kube-system get pod -o wide -l app=csi-nfs-node
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
csi-nfs-node-7s5zx 3/3 Running 0 4m2s 192.168.1.7 ubuntu02 <none> <none>
csi-nfs-node-w4kpp 3/3 Running 0 4m2s 192.168.1.9 ubuntu04 <none> <none>
csi-nfs-node-z65sn 3/3 Running 0 4m2s 192.168.1.8 ubuntu03 <none> <none>
root@ubuntu02:/home/k8s/csi-driver-nfs/deploy/v4.4.0# microk8s kubectl get csidrivers
NAME ATTACHREQUIRED PODINFOONMOUNT STORAGECAPACITY TOKENREQUESTS REQUIRESREPUBLISH MODES AGE
nfs.csi.k8s.io false false false <unset> false Persistent 5m29s
3.为NFS创建StorageClass
# 我们需要创建一个使用 nfs.csi.k8s.io CSI驱动程序的Kubernetes存储类。假设您已经配置了NFS共享 /srv/nfs ，并且NFS服务器的地址是 10.0.0.42 ，请创建以下文件：
# sc-nfs.yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: nfs-csi
provisioner: nfs.csi.k8s.io
parameters:
server: 10.1.31.0
share: /srv/nfs
reclaimPolicy: Delete
volumeBindingMode: Immediate
mountOptions:
- hard
- nfsvers=4.1
# 注意：上面YAML的最后一行表示NFS的特定版本。这应该与正在使用的NFS服务器的版本相匹配-如果您使用的是现有服务，请检查它使用的版本并进行相应调整。
# 然后在MicroK 8 s集群上应用：
microk8s kubectl apply -f sc-nfs.yaml
4.创建新PVC
# pvc-nfs.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: pv-claim
spec:
storageClassName: nfs-csi
accessModes: [ReadWriteOnce]
resources:
requests:
storage: 5Gi
# 然后创建PVC：
microk8s kubectl apply -f pvc-nfs.yaml
# 验证是否成功
root@ubuntu02:/home/k8s/nfs# microk8s kubectl describe pvc pv-claim
Name: pv-claim
Namespace: default
StorageClass: nfs-csi
Status: Bound
Volume: pvc-204c120b-123d-4343-a116-166f751ba616
Labels: <none>
Annotations: pv.kubernetes.io/bind-completed: yes
pv.kubernetes.io/bound-by-controller: yes
volume.beta.kubernetes.io/storage-provisioner: nfs.csi.k8s.io
volume.kubernetes.io/storage-provisioner: nfs.csi.k8s.io
Finalizers: [kubernetes.io/pvc-protection]
Capacity: 5Gi
Access Modes: RWO
VolumeMode: Filesystem
Used By: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Provisioning 2m31s nfs.csi.k8s.io_ubuntu04_b5d71960-e4c6-47f8-a498-4a1d4e90a399 External provisioner is provisioning volume for claim "default/pv-claim"
Normal ExternalProvisioning 2m31s (x2 over 2m31s) persistentvolume-controller waiting for a volume to be created, either by external provisioner "nfs.csi.k8s.io" or manually created by system administrator
Normal ProvisioningSucceeded 2m30s nfs.csi.k8s.io_ubuntu04_b5d71960-e4c6-47f8-a498-4a1d4e90a399 Successfully provisioned volume pvc-204c120b-123d-4343-a116-166f751ba616
