使用kubernetes1.20.*部署踩坑记 #190
Description
照着非Quick Start指南一步步操作，nfs都是没问题的，翻来覆去就是不成功，nacos的pods报错kubectl logs -f nacos-0 0/4 nodes are available: 4 pod has unbound immediate PersistentVolumeClaims.
这一行错误全网都没有解决方案，kubectl get pvc 3个都是pending,照这条路怎么也查不到，灵机一动想到看看nfs-client-provisioner日志吧，嘿好家伙错误日志如下：
I1231 09:05:32.221800 1 controller.go:987] provision "default/logdir-nacos-0" class "managed-nfs-storage": started
I1231 09:05:32.221840 1 controller.go:987] provision "default/plugindir-nacos-0" class "managed-nfs-storage": started
I1231 09:05:32.221965 1 controller.go:987] provision "default/datadir-nacos-0" class "managed-nfs-storage": started
E1231 09:05:32.235211 1 controller.go:1004] provision "default/plugindir-nacos-0" class "managed-nfs-storage": unexpected error getting claim reference: selfLink was empty, can't make reference
E1231 09:05:32.235253 1 controller.go:1004] provision "default/logdir-nacos-0" class "managed-nfs-storage": unexpected error getting claim reference: selfLink was empty, can't make reference
E1231 09:05:32.235464 1 controller.go:1004] provision "default/datadir-nacos-0" class "managed-nfs-storage": unexpected error getting claim reference: selfLink was empty, can't make reference
这一顿操作就明了了click here，原来是kubernetes1.20.0废弃了selfLink解决办法是重新加回来
vi /etc/kubernetes/manifests/kube-apiserver.yaml
## 增加一行
- --feature-gates=RemoveSelfLink=false
## 使之生效
kubectl apply -f /etc/kubernetes/manifests/kube-apiserver.yaml