# All components of kubernetes are repeatedly deleted and created **URL:** \ **Category:** General Discussions\ **Created:** [May 29, 2021, 1:54pm UTC](https://discuss.kubernetes.io/t/all-components-of-kubernetes-are-repeatedly-deleted-and-created/16088 "2021-05-29T13:54:56Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![aduncmj](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/aduncmj/32/7743_2.png) [@aduncmj](https://discuss.kubernetes.io/u/aduncmj)\ **Post date:** [May 29, 2021, 1:54pm UTC](https://discuss.kubernetes.io/t/all-components-of-kubernetes-are-repeatedly-deleted-and-created/16088/1 "2021-05-29T13:54:57Z")
Hi all, As shown below, the status of all components of k8s is between pending and running ![](https://us1.discourse-cdn.com/flex016/uploads/kubernetes/original/2X/2/252642c9958505383c7c41890ba3221e15d08f12.png) ![](https://us1.discourse-cdn.com/flex016/uploads/kubernetes/original/2X/7/7e3a29d33111d9894de3b6c7f0f6ea9d00f3130f.png) And logs from `journalctl -f -u kubelet` indicates pods are outdated. Some of detail logs are listed below. > 5月 21 17:42:14 k8s-master kubelet[1615]: E0521 17:42:14.168690 1615 kubelet.go:2167] Container runtime network not ready: NetworkReady=false reason:Ne > tworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized > 5月 21 17:42:15 k8s-master kubelet[1615]: W0521 17:42:15.733511 1615 kubelet.go:1622] Deleting mirror pod “etcd-k8s-master\_kube-system(d10c0f7f-ba18-11 > eb-84aa-0cc47adadbe0)” because it is outdated > 5月 21 17:42:15 k8s-master kubelet[1615]: W0521 17:42:15.740525 1615 kubelet.go:1622] Deleting mirror pod “kube-apiserver-k8s-master\_kube-system(d10c3d > 2e-ba18-11eb-84aa-0cc47adadbe0)” because it is outdated > 5月 21 17:42:15 k8s-master kubelet[1615]: W0521 17:42:15.749751 1615 kubelet.go:1622] Deleting mirror pod “kube-controller-manager-k8s-master\_kube-syst > em(d0af2526-ba18-11eb-84aa-0cc47adadbe0)” because it is outdated > 5月 21 17:42:15 k8s-master kubelet[1615]: W0521 17:42:15.756567 1615 kubelet.go:1622] Deleting mirror pod “kube-scheduler-k8s-master\_kube-system(d0b161 > f7-ba18-11eb-84aa-0cc47adadbe0)” because it is outdated > 5月 21 17:42:16 k8s-master kubelet[1615]: W0521 17:42:16.437473 1615 kubelet.go:1622] Deleting mirror pod “etcd-k8s-master\_kube-system(d10c0f7f-ba18-11 > eb-84aa-0cc47adadbe0)” because it is outdated > 5月 21 17:42:17 k8s-master kubelet[1615]: W0521 17:42:17.444155 1615 kubelet.go:1622] Deleting mirror pod “etcd-k8s-master\_kube-system(d3a06510-ba18-11 > eb-84aa-0cc47adadbe0)” because it is outdated > 5月 21 17:42:19 k8s-master kubelet[1615]: W0521 17:42:19.169992 1615 cni.go:188] Unable to update cni config: No networks found in /etc/cni/net.d Has anyone encountered this problem? What can I do for solving it? ### Cluster information: Kubernetes version: 1.12.9 Cloud being used: bare-metal Installation method: kubeadm Host OS: centos-7.9 CNI and version: contrail-k8s-cni CRI and version: docker 18.06 ---
**Author:** ![protosam](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/protosam/32/7732_2.png) [@protosam](https://discuss.kubernetes.io/u/protosam)\ **Post date:** [May 29, 2021, 3:04pm UTC](https://discuss.kubernetes.io/t/all-components-of-kubernetes-are-repeatedly-deleted-and-created/16088/2 "2021-05-29T15:04:22Z")
I don’t see the container for your CNI there and there are log entries saying it’s not ready. On a fresh cluster, I don’t think pods can reach a ready state until the CNI is ready. The error about deleting the mirror pod is probably irrelevant. That pod isn’t real and is just a abstraction from the kubelet process that runs on the node. Check the kubelet logs if you want to dig into that. ---
**Author:** ![macintoshprime](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/macintoshprime/32/7121_2.png) [@macintoshprime](https://discuss.kubernetes.io/u/macintoshprime)\ **Post date:** [May 29, 2021, 5:25pm UTC](https://discuss.kubernetes.io/t/all-components-of-kubernetes-are-repeatedly-deleted-and-created/16088/3 "2021-05-29T17:25:24Z")
Is there a reason you are running version `1.12.9`? If not might want to consider upgrading the latest release (current is `1.21`) and [support](https://kubernetes.io/releases/version-skew-policy/) only goes back 3 minor versions (`1.19`).