V3.2.1 nfs-client-nfs-client-provisioner 无法启动

spiderMan

操作系统信息
例如：华为云，Centos7.9

Kubernetes版本信息
Client Version: version.Info{Major:“1”, Minor:“21”, GitVersion:“v1.21.5”, GitCommit:“aea7bbadd2fc0cd689de94a54e5b7b758869d691”, GitTreeState:“clean”, BuildDate:“2021-09-15T21:10:45Z”, GoVersion:“go1.16.8”, Compiler:“gc”, Platform:“linux/amd64”}

Server Version: version.Info{Major:“1”, Minor:“21”, GitVersion:“v1.21.5”, GitCommit:“aea7bbadd2fc0cd689de94a54e5b7b758869d691”, GitTreeState:“clean”, BuildDate:“2021-09-15T21:04:16Z”, GoVersion:“go1.16.8”, Compiler:“gc”, Platform:“linux/amd64”}

容器运行时

Client:

Version: 20.10.8

API version: 1.41

Go version: go1.16.6

Git commit: 3967b7d

Built: Fri Jul 30 19:50:40 2021

OS/Arch: linux/amd64

Context: default

Experimental: true

Server: Docker Engine - Community

Engine:

Version: 20.10.8

API version: 1.41 (minimum version 1.12)

Go version: go1.16.6

Git commit: 75249d8

Built: Fri Jul 30 19:55:09 2021

OS/Arch: linux/amd64

Experimental: false

containerd:

Version: v1.4.9

GitCommit: e25210fe30a0a703442421b0f60afac609f950a3

runc:

Version: 1.0.1

GitCommit: v1.0.1-0-g4144b638

docker-init:

Version: 0.19.0

GitCommit: de40ad0

KubeSphere版本信息
例如：v2.1.1/v3.2.1。kk安装

问题是什么

nfs-client-nfs-client-provisioner 不可用

nfs:

server: “10.30.0.14:/”

path: “/mnt/data”

storageClass:

defaultClass: true

spiderMan

一直是容器创建中

Kyons

看看pod事件，是不是镜像没拉取下来。

spiderMan

Controlled By: ReplicaSet/nfs-client-nfs-client-provisioner-7794cfc5b5

Containers:

nfs-client-provisioner:

Container ID:   

Image:          registry.cn-beijing.aliyuncs.com/kubesphereio/nfs-subdir-external-provisioner:v4.0.2

Image ID:       

Port:           <none>

Host Port:      <none>

State:          Waiting

  Reason:       ContainerCreating

Ready:          False

Restart Count:  0

Environment:

  PROVISIONER_NAME:  cluster.local/nfs-client-nfs-client-provisioner

  NFS_SERVER:        10.30.0.14:/

  NFS_PATH:          /mnt/data

Mounts:

  /persistentvolumes from nfs-client-root (rw)

  /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-h8pkt (ro)

Conditions:

Type Status

Initialized True

Ready False

ContainersReady False

PodScheduled True

Volumes:

nfs-client-root:

Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)

ClaimName:  pvc-nfs-client-nfs-client-provisioner

ReadOnly:   false

kube-api-access-h8pkt:

Type:                    Projected (a volume that contains injected data from multiple sources)

TokenExpirationSeconds:  3607

ConfigMapName:           kube-root-ca.crt

ConfigMapOptional:       <nil>

DownwardAPI:             true

QoS Class: BestEffort

Node-Selectors: <none>

Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s

                         node.kubernetes.io/unreachable:NoExecute op=Exists for 300s

Events:

Type Reason Age From Message

Normal Scheduled 22s default-scheduler Successfully assigned kube-system/nfs-client-nfs-client-provisioner-7794cfc5b5-blwmr to ecs-k8s-node1

Warning FailedMount 6s (x4 over 19s) kubelet MountVolume.SetUp failed for volume “pv-nfs-client-nfs-client-provisioner” : mount failed: exit status 32

Mounting command: mount

Mounting arguments: -t nfs -o nolock,noresvport,timeo=600,vers=3 10.30.0.14:/:/mnt/data /var/lib/kubelet/pods/273f6c89-8471-43f2-be9b-635efe546848/volumes/kubernetes.io~nfs/pv-nfs-client-nfs-client-provisioner

Output: mount.nfs: access denied by server while mounting 10.30.0.14:/:/mnt/data

spiderMan

Output: mount.nfs: access denied by server while mounting 10.30.0.14:/:/mnt/data