[BUG] nfs provisioner too old and needs an update

释放双眼,带上耳机,听听看~!
🤖 由 ChatGPT 生成的文章摘要

I followed this page [1] to set up nfs with my k8s 1.25.
However the nfs client provisioner is too old and deprecated.
When creating a pvc, it is always pending.
Checking the provisioner log, it is complaining about selfLink being empty.

E0331 06:53:31.562497 1 controller.go:1004] provision "controller-myk8scloud/storage-controller-0" class "default": unexpected error getting claim reference: selfLink was empty, can't make reference

This issue [2] suggests we can fix that by adding "--feature-gates=RemoveSelfLink=false" to apiserver.
But the value RemoveSelfLink is always true from 1.24 [3][4] and can't be set to false.
So according to some comments of [2] I changed to "gcr.io/k8s-staging-sig-storage/nfs-subdir-external-provisioner:v4.0.0", which fixed the issue.
It seems nfs-subdir-external-provisioner is the replacement of nfs-client-provisioner [5]

My deployment looks like [6], and my storage class is like [7].
Please update templates/nfs-provisioner.yaml to use the new nfs-subdir-external-provisioner for k8s 1.24+.

解决办法:

  • 1.23之前可以关闭selfLink的方式
  • 1.24a之后更换镜像版本解决:
    gcr.io/k8s staging sig-storage/nfs-subdir external provisioner:v4.0.0

给TA打赏
共{{data.count}}人
人已打赏
Kafka报错锦集

Kafka Uncaught error in kafka producer I/O thread: (org.apache.kafka.clients.producer.internals.Sender) java.lang.IllegalStateException: No entry found for connection 0

2023-8-29 14:45:20

报错锦集

elasticsearch版本与jdk版本对应图

2023-9-14 0:37:28

0 条回复 A文章作者 M管理员
    暂无讨论,说说你的看法吧
个人中心
购物车
优惠劵
今日签到
有新私信 私信列表
搜索