Repository: kubernetes
Issue: k8s persistent volume (PV) data gets deleted after pod recreation with all ReclaimPolicy : Retain
Labels: kind/bug,sig/storage,priority/important-longterm,lifecycle/rotten,triage/needs-information,needs-triage

### What happened?

1) I created one PV(persistent volume) using .yaml file 10G on aws efs  "/data/flink/state"
2) created PVC of 10G and here we are using dynamic provisioning (storage-class) to mount PV.
3) created pod deployment using deploy.yaml file. here we are using FlinkOperator to deploy the application.
4) entered to pod using "kubectl exec -it flow-engine-598f45f7d6-qqv9p -- bash" to access the bash of the pod created.
5) Run the flink application which created the file on above mentioned path i.e "/data/flink/state"
6) now deleted the pod using "kubectl delete pod flow-engine-598f45f7d6-qqv9p
7) now again new pod gets created after deleting the above pod and I accessed the bash of the new pod again
8) And I don't see a file created inside the mount path "/data/flink/state", this file got deleted.


What happened:
after every deletion of the pod, the data will get deleted from that mounted path.



### What did you expect to happen?

What you expected to happen:
Retain policy: data should be available after every pod recreation unless PV is deleted. And we can able to fetch that data.

### How can we reproduce it (as minimally and precisely as possible)?

1. create a namespace
2. create PV / PVC / and deployment kind pod with local mount path without using any other storage location.
3. Access the pod bash console and write a file inside the mount path of the pod and exit
4. delete the pod and it will automatically recreate the pod.
5. now again access bash of newly recreated pod and check file exist or not.

### Anything else we need to know?


attached below .yaml file used for creating PVC and storage-class


pvc.yaml
persistentVolumeClaim:
      spec:
        storageClassName: mkt-efs-sc
        accessModes:
          - ReadWriteMany
        resources:
          requests:
            storage: 10Gi


storage-class.yaml
 storageClass:
     provisioner: efs.csi.aws.com
     reclaimPolicy: Retain
     parameters:
       fileSystemId:  <efs-id>
       provisioningMode: efs-ap
       directoryPerms: "777"

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.3", GitCommit:"25b4e43193bcda6c7328a6d147b1fb73a33f1598", GitTreeState:"clean", BuildDate:"2023-06-15T02:15:11Z", GoVersion:"go1.20.5", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"23+", GitVersion:"v1.23.17-eks-c12679a", GitCommit:"d5ce2cee85d99653d6f8c278043213db21b1cd72", GitTreeState:"clean", BuildDate:"2023-05-22T20:32:28Z", GoVersion:"go1.19.6", Compiler:"gc", Platform:"linux/amd64"}

```

</details>


### Cloud provider

<details>
provider: aws/efs
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>