This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 22%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET5%3C/text%3E%3C/svg%3E)
We are running a stateful application on AKS and required persistent volume. PVC will be shared by multiple pods.
We are using Azure Files premium over NFS for Dynamic PVs. The PVCs are defined with 'ReclaimPolicy: Retain' and AccessModes as 'ReadWriteMany'.
Whenever we delete the PVC it triggers a resize in PV share, the share decrease to the size specified for another PVC in the same PV.
Further, creating a new PVC with size higher than PV share size - doesn't trigger auto increase.
If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!
You mentioned that the PVCs are defined with ReclaimPolicy: Retain. This policy ensures that the underlying physical storage is not automatically deleted when the PVC is deleted. However, this policy does not control the resizing behavior of the Fileshare, so check this old thread : https://github.com/kubernetes/kubernetes/issues/88683