directory created in persistent volume claim disk not deleted when the resources is deleted

[johnmba]

I have been this issue for some days now and I have used so many approach I could find in googling but have keep having the same issue.
The issue is that I claimed a persistent volume for a postgresql database but because there was an error in the initialization script, I deleted the the deployment and persistent volume claim through

• kubectl kubectl delete deployments --all then kubectl delete pvc --all
• through the gcloud command in the command line gcloud compute delete pvc-19874143-f6ec-4808-85eb-c1f3e3572294

The issues is that when I recreate the resources, and deploy my database, the initialization is skipped and the permission right on the existing directory is being fixed as shown in the pod logs kubectl logs <pod name>

The expectation is that the database is initialized since the persistent volume has been deleted and recreated, hence, the previous directory shouldn't exists.

[k8s-ci-robot]

This issue is currently awaiting triage.

If the repository mantainers determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.