Migrated VMs that has Kubernetes from AWS to Azure but we are unable to get the calico and coredns pods running.

[sharan kumar]

Hi Team,

We have Migrated kubenetes rhel8 VMs from AWS to Azure.

on Azure we have updated all the kubernetes configs and have restarted kubelet service 

calico and coredns pods are in unknown state, For this  issues as troubleshooting we have tried to delete the calico pods but they are not getting created.

Could some one please suggest how to bring these pods to running state. Have posted the same question on many forums but could not get any responses.

[root@master01 net.d]# kubectl get pods -n kube-system -o wide
NAME                                           READY   STATUS    RESTARTS       AGE   IP         NODE                   NOMINATED NODE   READINESS GATES
calico-kube-controllers-564985c589-m6ttv       0/1     Unknown   12             17d   <none>     master01.example.com   <none>           <none>
calico-node-lzcl8                              0/1     Unknown   12             17d   10.5.0.5   master01.example.com   <none>           <none>
calico-node-x5284                              0/1     Unknown   8              17d   10.5.0.4   worker01.example.com   <none>           <none>
coredns-55cb58b774-knfbm                       0/1     Unknown   12             17d   <none>     master01.example.com   <none>           <none>
coredns-55cb58b774-lj5mm                       0/1     Unknown   12             17d   <none>     master01.example.com   <none>           <none>
etcd-master01.example.com                      1/1     Running   2 (63m ago)    23h   10.5.0.5   master01.example.com   <none>           <none>
kube-apiserver-master01.example.com            1/1     Running   2 (63m ago)    23h   10.5.0.5   master01.example.com   <none>           <none>
kube-controller-manager-master01.example.com   1/1     Running   16 (63m ago)   17d   10.5.0.5   master01.example.com   <none>           <none>
kube-proxy-l8shz                               1/1     Running   15 (63m ago)   17d   10.5.0.5   master01.example.com   <none>           <none>
kube-proxy-p28ff                               1/1     Running   11 (64m ago)   17d   10.5.0.4   worker01.example.com   <none>           <none>
kube-scheduler-master01.example.com            1/1     Running   16 (63m ago)   17d   10.5.0.5   master01.example.com   <none>           <none>
[root@master01 net.d]#



[root@master01 net.d]# kubectl get nodes -o wide
NAME                   STATUS   ROLES           AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                               KERNEL-VERSION
              CONTAINER-RUNTIME
master01.example.com   Ready    control-plane   17d   v1.30.8   10.5.0.5      <none>        Red Hat Enterprise Linux 8.4 (Ootpa)   4.18.0-305.82.1.el8_4.x86_64   containerd://1.7.25
worker01.example.com   Ready    <none>          17d   v1.30.8   10.5.0.4      <none>        Red Hat Enterprise Linux 8.4 (Ootpa)   4.18.0-305.82.1.el8_4.x86_64   containerd://1.7.25
[root@master01 net.d]#

Regards,

Sharan

[rac...@rundeck.com]

Hi Sharan,

Is this related to Rundeck? I assume it's an open question :-)

Regards.

[sharan kumar]

Hi Team,

It's an open question.

Regards,

Sharan 

--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/rundeck-discuss/cc8ef3d8-c1d4-423d-b837-a3303b9a3340n%40googlegroups.com.