Comment 5 for bug 2021891

I understand that the local container file system is not durable. I'm still confused about why for some pod churns (i.e. `kubectl delete`) the charm gets an `upgrade-charm` event after the new pod starts but for other pod churns (i.e. `microk8s stop`) the charm does not get that event. From the debug log, it's clear that juju detected a reboot.

Currently, `upgrade-charm` being fired on `kubectl delete` suggests that charm developers can use that event to detect a pod restart—but it detects only some pod restarts.

Is there a reason that `upgrade-charm` is currently fired after `kubectl delete`?