PVC does not re-bind to PV after it is deleted and redeployed

General:

• [ x] Have you removed all sensitive information, including but not limited to access keys and passwords?
• [x ] Have you checked to ensure there aren't other open or closed Pull Requests for the same bug/feature/question?

Feature Requests:

• Have you explained your rationale for why this feature is needed?
• Have you offered a proposed implementation/solution?

Bug Reporting

Expected Behavior

The claimRef should be deleted upon PVC deletion

Actual Behavior

claimRef does not delete, so it has to be done manually in order for the PVC to bind

Steps to Reproduce the Problem

New cluster was deployed, and same issue was experienced

Additional Notes

This was based on a Community site question, which I will link here. The dev-lke team was able to reproduce the issue and it looked to them as though it may be a bug:

https://www.linode.com/community/questions/21149/how-do-i-rebind-a-pv-when-pvc-gets-re-instated

For general help or discussion, join the Kubernetes Slack team channel #linode. To sign up, use the Kubernetes Slack inviter.

The Linode Community is a great place to get additional support.

Start by reproducing the PVC deletion and redeployment flow on a new cluster, then inspect how the CSI driver handles the PV claimRef during that lifecycle. Done means the claimRef is cleared automatically and the recreated PVC binds to the PV without manual intervention, with regression coverage for the reproduced case.