Minikube 在重启时总是重置为初始状态
Minikube always reset to initial state when restart it
我从昨天开始遇到这个问题,之前没有问题。
我的环境是
- Windows11
- Docker 桌面版 4.4.4
- minikube 1.25.1
- kubernetes-cli 1.23.3
重现
1。启动 minikube 并创建集群
minikube start
2。检查 pods
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
3。添加新 pod(在本例中,使用 istio)
istioctl manifest apply -y
4。检查 pods
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
5。重启 minikube
minikube stop
然后,回到 1 并检查 pod,kubectl get po -A
returns 与 #2.
相同 pods
(在这种情况下,istio-system 丢失了。)
已创建 pods 等保留到昨天甚至重启 minikube 或 PC。
有没有人遇到同样的问题或者有什么解决办法?
这似乎是 1.25.0 版 minikube 引入的错误:https://github.com/kubernetes/minikube/issues/13503。
恢复引入错误的更改的 PR 已经打开:https://github.com/kubernetes/minikube/pull/13506
修复计划用于 minikube v1.26。
跟着@CdrBlair,我检查了changelog and this is actually already implemented into Version 1.25.2 - 2022-02-23
Bug Fixes:
- Fix losing cluster on restart #13506
太棒了。我也很惭愧地发现我的集群被删除了♂️
我从昨天开始遇到这个问题,之前没有问题。
我的环境是
- Windows11
- Docker 桌面版 4.4.4
- minikube 1.25.1
- kubernetes-cli 1.23.3
重现
1。启动 minikube 并创建集群
minikube start
2。检查 pods
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
3。添加新 pod(在本例中,使用 istio)
istioctl manifest apply -y
4。检查 pods
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
5。重启 minikube
minikube stop
然后,回到 1 并检查 pod,kubectl get po -A
returns 与 #2.
相同 pods
(在这种情况下,istio-system 丢失了。)
已创建 pods 等保留到昨天甚至重启 minikube 或 PC。
有没有人遇到同样的问题或者有什么解决办法?
这似乎是 1.25.0 版 minikube 引入的错误:https://github.com/kubernetes/minikube/issues/13503。 恢复引入错误的更改的 PR 已经打开:https://github.com/kubernetes/minikube/pull/13506
修复计划用于 minikube v1.26。
跟着@CdrBlair,我检查了changelog and this is actually already implemented into Version 1.25.2 - 2022-02-23
Bug Fixes:
- Fix losing cluster on restart #13506
太棒了。我也很惭愧地发现我的集群被删除了♂️