部署到nfs测试不通过

  • Choerodon平台版本: v0.25

  • 遇到问题的执行步骤:
    [vagrant@localhost ~]$ helm upgrade --install nfs-client-provisioner c7n/nfs-client-provisioner \

–set rbac.create=true
–set persistence.enabled=true
–set storageClass.name=nfs-provisioner
–set persistence.nfsServer=127.0.0.1
–set persistence.nfsPath=/u01/prod
–version 0.1.1
–namespace kube-system
Release “nfs-client-provisioner” has been upgraded. Happy Helming!
NAME: nfs-client-provisioner
LAST DEPLOYED: Wed May 26 16:47:38 2021
NAMESPACE: kube-system
STATUS: deployed
REVISION: 2
TEST SUITE: None

[vagrant@localhost ~]$ cat /etc/exports
/u01 10.8.0.0/24 (rw,sync,insecure,no_subtree_check,no_root_squash)

[vagrant@localhost ~]$ showmount -e 127.0.0.1
Export list for 127.0.0.1:
/u01 (everyone)

在 验证 安装 nfs-client-provisioner 这一步
测试状态一直是Pending状态 无法进一步往下部署
[vagrant@localhost ~]$ kubectl get po
NAME READY STATUS RESTARTS AGE
write-pod 0/1 Pending 0 15s

  • 文档地址:

  • 环境信息(如:节点信息):
    主机环境 centos7.9
    nfs服务在10.8.0.120
    [vagrant@localhost ~]$ df -h
    Filesystem Size Used Avail Use% Mounted on
    devtmpfs 16G 0 16G 0% /dev
    tmpfs 16G 0 16G 0% /dev/shm
    tmpfs 16G 43M 16G 1% /run
    tmpfs 16G 0 16G 0% /sys/fs/cgroup
    /dev/mapper/centos-root 138G 4.6G 133G 4% /
    /dev/sda1 497M 144M 354M 29% /boot
    /dev/mapper/vg1-lv1 1.2T 33M 1.2T 1% /u01

[vagrant@localhost ~]$ kubectl get node
NAME STATUS ROLES AGE VERSION
10.8.0.120 Ready control-plane,etcd,master,worker 6d1h v1.16.15
10.8.0.121 Ready control-plane,etcd,master,worker 6d1h v1.16.15
10.8.0.122 Ready control-plane,etcd,master,worker 6d1h v1.16.15
10.8.0.123 Ready worker 6d v1.16.15
[vagrant@localhost ~]$ systemctl status nfs-server
● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled)
Drop-In: /run/systemd/generator/nfs-server.service.d
└─order-with-mounts.conf
Active: active (exited) since Wed 2021-05-26 08:42:54 CST; 8h ago

  • 报错日志:
    [vagrant@localhost ~]$ kubectl describe pod

Events:
Type Reason Age From Message


Warning FailedScheduling default-scheduler persistentvolumeclaim “myclaim” not found
Warning FailedScheduling default-scheduler persistentvolumeclaim “myclaim” not found

  • 原因分析:

    提出您分析问题的过程,以便我们能更准确的找到问题所在

  • 疑问:

    提出您对于遇到和解决该问题时的疑问

–set persistence.nfsServer=127.0.0.1 应该设置为你的 nfs 服务器 IP

nfs 服务就是在本机,然后我试了用本机Ip 也是不行的
[vagrant@localhost ~]$ showmount -e 10.8.0.120
Export list for 10.8.0.120:
/u01/prod (everyone)
[vagrant@localhost ~]$ helm upgrade --install nfs-client-provisioner c7n/nfs-client-provisioner --set rbac.create=true --set persistence.enabled=true --set storageClass.name=nfs-provisioner --set persistence.nfsServer=10.8.0.120 --set persistence.nfsPath=/u01/prod --version 0.1.1 --namespace kube-system
Release “nfs-client-provisioner” has been upgraded. Happy Helming!
NAME: nfs-client-provisioner
LAST DEPLOYED: Thu May 27 11:21:07 2021
NAMESPACE: kube-system
STATUS: deployed
REVISION: 3
TEST SUITE: None

[vagrant@localhost ~]$ kubectl apply -f write-pod.yaml
pod/write-pod created
persistentvolumeclaim/myclaim created
[vagrant@localhost ~]$ kubectl get po
NAME READY STATUS RESTARTS AGE
write-pod 0/1 Pending 0 2s
[vagrant@localhost ~]$ kubectl get po
NAME READY STATUS RESTARTS AGE
write-pod 0/1 Pending 0 103s