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

[wan766405890]

k8s version:1.25.4

Add this line:
--feature-gates=RemoveSelfLink=false
The do this:
kubectl apply -f /etc/kubernetes/manifests/kube-apiserver.yaml
kubectl apply -f /etc/kubernetes/manifests/kube-apiserver.yaml

kubelet goes down and throw error

[GizzmoAsus]

hey @wan766405890, not sure if you've resolved this or not but SelfLink was removed from Kubernetes in version 1.21 so the work around won't work.

I was able to resolve this by using the image referenced in #25, I just had to update the deployment yaml in my kubernetes cluster once the helm chart had deployed it to swap out the image and now it's working. Doesn't solve the issue but is an easy work around for my dev environment. Please note, the replacement image was last updated 3 years ago so may not be suitable for PDC environments.

The PR #258 is still pending which looks like it will also resolve this issue properly.

[yonatankahana]

@GizzmoAsus
can you verify if problem solved in the next version rc image: quay.io/yonatankahana/nfs-subdir-external-provisioner:v4.0.3-rc1?

For helm use: --set image.repository=quay.io/yonatankahana/nfs-subdir-external-provisioner,image.tag=v4.0.3-rc1

[GizzmoAsus]

hey @yonatankahana, switching my image out to the one you provided does indeed work just fine :)

For reference, I'm running a Kubernetes cluster @ v1.27.4

[yonatankahana]

excellent, hopefully new version will be released soon, follow #291

[GizzmoAsus]

Brilliant, I'll keep an eye out for the release and continue using the RC in the meantime, thank you :)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.