PV detach from shutdown node

[lavalex]

Hello,

When node goes down, pod is deployed on another node, but NFS mount stays "attached" to the failed node. Is it expected to happen?

Thanks.

[niranjandarshann]

@lavalex Yes, it’s expected that NFS mounts stay attached when a node fails.

[niranjandarshann]

If a node goes down unexpectedly, Kubernetes does not immediately clean up or forcefully unmount the NFS volume.
The PV remains "attached" to the failed node until Kubernetes detects the failure.

[niranjandarshann]

One Approach that is common check persistentVolumeReclaimPolicy in pv.yaml and check it should be Retain i think this may fix it. As this approach is actively taken and work for majority of the people.

[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 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