mount: wrong fs type, bad option, bad superblock on 10.0.2.60:/opt/module/nfs/data

Events:
  Type     Reason       Age                 From               Message
  ----     ------       ----                ----               -------
  Normal   Scheduled    2m3s                default-scheduler  Successfully assigned default/nfs-client-provisioner-6f5c7f957-cwd5b to k8s-compute-01
  Warning  FailedMount  60s (x8 over 2m4s)  kubelet            MountVolume.SetUp failed for volume "nfs-client-root" : mount failed: exit status 32
Mounting command: mount
Mounting arguments: -t nfs 10.0.2.60:/opt/module/nfs/data /var/lib/kubelet/pods/f318e6e9-6a2d-4b5f-8e26-507f1b903658/volumes/kubernetes.io~nfs/nfs-client-root
Output: mount: wrong fs type, bad option, bad superblock on 10.0.2.60:/opt/module/nfs/data,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
  Warning  FailedMount  1s  kubelet  Unable to attach or mount volumes: unmounted volumes=[nfs-client-root], unattached volumes=[nfs-client-root kube-api-access-k8sc9]: timed out waiting for the condition

检查所有节点（避免provisioner pod 部署在未安装nfs 的节点上）是否安装 nfs

yum install -y nfs-common nfs-utils

unexpected error getting claim reference: selfLink was empty, can’t make reference

[root@hadoop03 NFS]# cat /etc/kubernetes/manifests/kube-apiserver.yaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    kubeadm.kubernetes.io/kube-apiserver.advertise-address.endpoint: 192.168.153.103:6443
  creationTimestamp: null
  labels:
    component: kube-apiserver
    tier: control-plane
  name: kube-apiserver
  namespace: kube-system
spec:
  containers:
  - command:
    - kube-apiserver
    - --advertise-address=192.168.153.103
    ### 添加这行 ###
    - --feature-gates=RemoveSelfLink=false