Comment 4 for bug 2021891

k8s guarantees the pod identity of stateful set pods, but they can be rescheduled as needed to satisfy various constraints. If a pod is rescheduled, any PV will get reattached, but the local file system will not be restored. This is just standard k8s behaviour the charm needs to deal with. It must not assume that info stored on the local container file system is durable. Anything that needs to be persisted across pod restarts (for whatever reason) needs to be put into unit state (for config. key pairs etc), or on a storage volume declared in te charm metadata.