Intermittent Volume Mounting Error

[atilsensalduz]

Hello everyone, I've been encountering an intermittent issue in my Kubernetes environment especially in under load and I was hoping to get some insight into what might be causing it. Occasionally, I see the following error message in the Kubernetes events:

Unable to attach or mount volumes: unmounted volumes=[config-volume-5favqh58-jv5hu1f5 keys-volume-5favqh58-jv5hu1f5 persistence-jv5hu1f5 kube-api-access-bf5b7], 
unattached volumes=[], failed to process volumes=[persistence-jv5hu1f5]: 
error processing PVC -5favqh58/persistence-jv5hu1f5-5favqh58-jv5hu1f5-46-1: failed to fetch PVC from API server: 
persistentvolumeclaims \"persistence-jv5hu1f5-5favqh58-jv5hu1f5-46-1\" is forbidden: User \"system:node:ip-10-10-10-10.us-east-2.compute.internal\" 
cannot get resource \"persistentvolumeclaims\" in API group \"\" in the namespace \"5favqh58\": 
no relationship found between node 'ip-10-10-10-10.us-east-2.compute.internal' and this object

It doesn't happen all the time, which makes it more perplexing. I've been suspecting that it might be related to some rate limits or perhaps an issue with handling requests from the EKS control plane side, but I'm not entirely sure. Has anyone else encountered a similar issue before? Or does anyone have any insights into what might be causing this error? Any help or suggestions would be greatly appreciated! Thanks in advance

/triage support

[k8s-ci-robot]

@atilsensalduz: The label(s) triage/support cannot be applied, because the repository doesn't have them.

In response to this:

Hello everyone, I've been encountering an intermittent issue in my Kubernetes environment especially in under load and I was hoping to get some insight into what might be causing it. Occasionally, I see the following error message in the Kubernetes events:

Unable to attach or mount volumes: unmounted volumes=[config-volume-5favqh58-jv5hu1f5 keys-volume-5favqh58-jv5hu1f5 persistence-jv5hu1f5 kube-api-access-bf5b7], 
unattached volumes=[], failed to process volumes=[persistence-jv5hu1f5]: 
error processing PVC -5favqh58/persistence-jv5hu1f5-5favqh58-jv5hu1f5-46-1: failed to fetch PVC from API server: 
persistentvolumeclaims \"persistence-jv5hu1f5-5favqh58-jv5hu1f5-46-1\" is forbidden: User \"system:node:ip-10-10-10-10.us-east-2.compute.internal\" 
cannot get resource \"persistentvolumeclaims\" in API group \"\" in the namespace \"5favqh58\": 
no relationship found between node 'ip-10-10-10-10.us-east-2.compute.internal' and this object

It doesn't happen all the time, which makes it more perplexing. I've been suspecting that it might be related to some rate limits or perhaps an issue with handling requests from the EKS control plane side, but I'm not entirely sure. Has anyone else encountered a similar issue before? Or does anyone have any insights into what might be causing this error? Any help or suggestions would be greatly appreciated! Thanks in advance

/triage support

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.

[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

[AndrewSirenko]

/remove-lifecycle rotten

[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