k8s mount nfs problem.
Error 1:
Please install on all k8s node nodes:
yum -y install nfs-utils
Error 2:
kubectl logs nfs-client-provisioner-59fd564b9b-zkpbn
Kubernetes PVC has been in Pending state
unexpected error getting claim reference: selfLink was empty, can’t make reference
Error 1:
Please install on all k8s node nodes:
yum -y install nfs-utils
Error 2:
kubectl logs nfs-client-provisioner-59fd564b9b-zkpbn
Kubernetes PVC has been in Pending state
unexpected error getting claim reference: selfLink was empty, can’t make reference
Temporary solution:
1.20.4 version, solution
/etc/kubernetes/manifests/kube-apiserver.yaml add “–feature-gates=RemoveSelfLink=false”
1.20.4 version, solution
/etc/kubernetes/manifests/kube-apiserver.yaml add “–feature-gates=RemoveSelfLink=false”
Solution-use version v4.0.x
Use nfs-client-provisioner: v4.0.1 here
Related documents: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/issues/25
Use easzlab/nfs-subdir-external-provisioner:v4.0.1 directly here
Use nfs-client-provisioner: v4.0.1 here
Related documents: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/issues/25
Use easzlab/nfs-subdir-external-provisioner:v4.0.1 directly here
Similar Posts:
- K8s version 1.20x nfs dynamic storage error: persistentvolume-controller waiting for a volume to be created, either by external provisioner “qgg-nfs-storage” or manually created by system administrator
- [Solved] Etcd cluster startup error: k8s-master01 systemd: Failed to start Etcd Service.
- 413 errors are reported in the service exposed by ingress
- Other Master Nodes Add to the Cluster After Reset Error: CONTEXT DEADLINE EXCEEDED
- k8s Error: [ERROR FileAvailable–etc-kubernetes-kubelet.conf]: /etc/kubernetes/kubelet.conf already exists
- Kubernetes: 413 request entity too large
- Kubectl’s plug-in management tool Krew
- [Solved] k8s ingress-nginx Error: 413 Request Entity Too Large
- K8s Run ingress yaml File Error: error when creating “ingress-myapp.yaml”: Internal error occurred: failed calling webhook
- [Solved] kubeadm join 192.168.50.66:6443 –token 0109we.c3a3ofn0y0lmp0w9 –discovery-token-ca-cert-hash sha256:262f5eefdbeba51e6875cba5ed6e34061ad679f8a21f6e295d9fbd5ef05757e4