Использую local-volume-provisioner, машина перезагрузилась, в директориях PV файлы сохранились, но

внутри контейнеров волумы будто не примаунтились, там создались дефолтные файлы. как такое может быть?

$ ls -al /mnt/kubernetes/1/grafana.db
-rw-r----- 1 1001 1001 2207744 Apr 3 18:22 /mnt/kubernetes/1/grafana.db

$ kubectl exec -it -n grafana grafana-6659796bc-d5r2j -- ls -al /opt/bitnami/grafana/data/grafana.db
-rw-r----- 1 1001 1001 765952 Apr 7 16:56 /opt/bitnami/grafana/data/grafana.db

$ kubectl describe pv local-pv-c7a8d68b
Name: local-pv-c7a8d68b
Labels: <none>
Annotations: pv.kubernetes.io/bound-by-controller: yes
pv.kubernetes.io/provisioned-by: local-volume-provisioner
Finalizers: [kubernetes.io/pv-protection]
StorageClass: default
Status: Bound
Claim: grafana/grafana
Reclaim Policy: Delete
Access Modes: RWO
VolumeMode: Filesystem
Capacity: 157Gi
Node Affinity:
Required Terms:
Term 0: kubernetes.io/hostname in [xxxx]
Message:
Source:
Type: LocalVolume (a persistent volume backed by local storage on a node)
Path: /mnt/kubernetes/1
Events: <none>

Дай описание пода в части вольюма

Только это и не кинул))

$ kubectl describe -n grafana pod grafana-6659796bc-d5r2j Name: grafana-6659796bc-d5r2j Namespace: grafana Priority: 0 Node: xxxx/192.168.100.141 Start Time: Thu, 07 Apr 2022 16:15:56 +0000 Labels: app.kubernetes.io/component=grafana app.kubernetes.io/instance=grafana app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=grafana helm.sh/chart=grafana-7.3.0 pod-template-hash=6659796bc Annotations: checksum/config: 96e97b7c2088c5e518425aa6614e0ee7562760bb5899a44ae0f68fdfbaa64adb checksum/dashboard-provider: 01ba4719c80b6fe911b091a7c05124b64eeece964e09c058ef8f9805daca546b checksum/secret: 588a5e20087a940a3826210972bfca6c3de5ca0a6521a3b93c0f00b009822ba0 kubectl.kubernetes.io/restartedAt: 2022-04-07T16:15:56Z Status: Running IP: 10.0.0.111 IPs: IP: 10.0.0.111 Controlled By: ReplicaSet/grafana-6659796bc Containers: grafana: Container ID: containerd://3725e662a6d6e95933caa930dab2745a149a091dfea48164a1d4491e2d2fb3da Image: docker.io/bitnami/grafana:8.3.3-debian-10-r0 Image ID: docker.io/bitnami/grafana@sha256:eb4f3538ac7325d0feae9e3a19c63de561e57b468069fc4336b6db1dbbff246b Port: 3000/TCP Host Port: 0/TCP State: Running Started: Thu, 07 Apr 2022 16:15:58 +0000 Ready: True Restart Count: 0 Liveness: http-get http://:dashboard/api/health delay=120s timeout=5s period=10s #success=1 #failure=6 Readiness: http-get http://:dashboard/api/health delay=30s timeout=5s period=10s #success=1 #failure=6 Environment Variables from: grafana-envvars ConfigMap Optional: false Environment: GF_SECURITY_ADMIN_PASSWORD: <set to the key 'GF_SECURITY_ADMIN_PASSWORD' in secret 'grafana-admin'> Optional: false Mounts: /opt/bitnami/grafana/data from data (rw) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: data: Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace) ClaimName: grafana ReadOnly: false QoS Class: BestEffort Node-Selectors: <none> Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 52m default-scheduler Successfully assigned grafana/grafana-6659796bc-d5r2j to xxxx Normal Pulled 52m kubelet Container image "docker.io/bitnami/grafana:8.3.3-debian-10-r0" already present on machine Normal Created 52m kubelet Created container grafana Normal Started 52m kubelet Started container grafana Warning NodeNotReady 23m (x2 over 27m) node-controller Node is not ready