minikube: Deleted hostpath PVs stuck in released state after minikube restart

Dynamically provisioned PVs are stuck in the released state if minikube is restarted before deleting the pvc. It seems that the Provisioner Identity changes on reboot which causes the hostpath provisioner to ignore the PV.

The exact command to reproduce the issue:

cat << EOF | kubectl apply -f -
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: mypvc
spec:
  resources:
    requests:
      storage: 10Mi
  accessModes:
    - ReadWriteOnce
EOF

minikube stop
minikube start
kubectl delete pvc mypvc
kubectl get pv

The full output of the command that failed:

$ minikube ssh tail /tmp/storage-provisioner.INFO
...
I0620 17:17:11.727823       1 controller.go:1040] deletion of volume "pvc-8674aa0d-937a-11e9-b2aa-000c29bcb67d" ignored: ignored because identity annotation on PV does not match ours

The output of the minikube logs command: N/A

The operating system version: MacOS 10.14.5 minikube v1.1.1 kubernetes 1.14.3