<p>I faced this problem since yesterday, no problems before.<br />
My environment is</p>
<ul>
<li>Windows 11</li>
<li>Docker Desktop 4.4.4</li>
<li>minikube 1.25.1</li>
<li>kubernetes-cli 1.23.3</li>
</ul>
<h1>Reproduce</h1>
<h2>1. Start minikube and create cluster</h2>
<pre><code>minikube start
</code></pre>
<h2>2. Check pods</h2>
<pre><code>kubectl get po -A

NAMESPACE     NAME                               READY   STATUS    RESTARTS   AGE
kube-system   coredns-64897985d-z7rpf            1/1     Running   0          22s
kube-system   etcd-minikube                      1/1     Running   1          34s
kube-system   kube-apiserver-minikube            1/1     Running   1          34s
kube-system   kube-controller-manager-minikube   1/1     Running   1          33s
kube-system   kube-proxy-zdr9n                   1/1     Running   0          22s
kube-system   kube-scheduler-minikube            1/1     Running   1          34s
kube-system   storage-provisioner                1/1     Running   0          29s
</code></pre>
<h2>3. Add new pod (in this case, use istio)</h2>
<pre><code>istioctl manifest apply -y
</code></pre>
<h2>4. Check pods</h2>
<pre><code>kubectl get po -A

NAMESPACE      NAME                                  READY   STATUS    RESTARTS      AGE
istio-system   istio-ingressgateway-c6d9f449-nhbvg   1/1     Running   0             13s
istio-system   istiod-5ffcccb477-5hzgs               1/1     Running   0             19s
kube-system    coredns-64897985d-nxhxm               1/1     Running   0             67s
kube-system    etcd-minikube                         1/1     Running   2             79s
kube-system    kube-apiserver-minikube               1/1     Running   2             82s
kube-system    kube-controller-manager-minikube      1/1     Running   2             83s
kube-system    kube-proxy-8jfz7                      1/1     Running   0             67s
kube-system    kube-scheduler-minikube               1/1     Running   2             83s
kube-system    storage-provisioner                   1/1     Running   1 (45s ago)   77s
</code></pre>
<h2>5. Restart minikube</h2>
<pre><code>minikube stop
</code></pre>
<p>then, back to 1 and and check pod, <code>kubectl get po -A</code> returns same pods as <strong>#2</strong>.<br />
(In this case, istio-system is lost.)</p>
<p>Created pods etc. was retained till yesterday even restart minikube or PC.</p>
<p>Does anyone face same problem or have any solution?</p>

akrsum
<p>This seems to be a bug introduced with 1.25.0 version of minikube: <a href="https://github.com/kubernetes/minikube/issues/13503" rel="nofollow noreferrer">https://github.com/kubernetes/minikube/issues/13503</a> .
A PR to revert the changes introducing the bug is already open: <a href="https://github.com/kubernetes/minikube/pull/13506" rel="nofollow noreferrer">https://github.com/kubernetes/minikube/pull/13506</a></p>
<p>The fix is scheduled for minikube v1.26.</p>
