Comment 3 for bug 2021891

In the case of microk8s stop / start, there appears to be pod churn—a different pod starts when the cluster comes up again

Steps to reproduce:
1. juju add-model foo
2. juju deploy mysql-k8s --channel 8.0/edge --trust
3. juju deploy mysql-router-k8s --channel 8.0/edge
4. juju relate mysql-router-k8s mysql-k8s
5. Wait for idle
6. kubectl -n foo describe pod mysql-router-k8s-0 # Look at container `Restart Count` (should be 0) or State start time
7. kubectl -n foo exec mysql-router-k8s-0 --container mysql-router -- ls /etc/mysqlrouter # Two files exist
8. sudo microk8s stop
9. sudo microk8s start
10. kubectl -n foo exec mysql-router-k8s-0 --container mysql-router -- ls /etc/mysqlrouter # No files exist
11. kubectl -n foo describe pod mysql-router-k8s-0 # Container restart count is 1, state start time is newer, last state is terminated