Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
895 views
in Technique[技术] by (71.8m points)

debian buster - Kubernetes API container dies constantly

I just installed from scratch a small Kubernetes test cluster in a 4 Armbian/Odroid_MC1 (Debian 10) nodes. The install process is this 1, nothing fancy or special, adding k8s apt repo and install with apt.

The problem is that the API server dies constantly, like every 5 to 10 minutes, after the controller-manager and the scheduler die together, who seem to stop simultaneously before. Evidently, the API becomes unusable for like a minute. All three services do restart, and things run fine for the next four to nine minutes, when the loop repeats. Logs are here 2. This is an excerpt:

$ kubectl get pods -o wide --all-namespaces

The connection to the server 192.168.1.91:6443 was refused - did you specify the right host or port?

(a minute later)

$ kubectl get pods -o wide --all-namespaces

NAMESPACE     NAME                          READY   STATUS    RESTARTS   AGE   IP             NODE   NOMINATED NODE   READINESS GATES
kube-system   coredns-74ff55c5b-8pm9r       1/1     Running   2          88m   10.244.0.7     mc1    <none>           <none>
kube-system   coredns-74ff55c5b-pxdqz       1/1     Running   2          88m   10.244.0.6     mc1    <none>           <none>
kube-system   etcd-mc1                      1/1     Running   2          88m   192.168.1.91   mc1    <none>           <none>
kube-system   kube-apiserver-mc1            0/1     Running   12         88m   192.168.1.91   mc1    <none>           <none>
kube-system   kube-controller-manager-mc1   1/1     Running   5          31m   192.168.1.91   mc1    <none>           <none>
kube-system   kube-flannel-ds-fxg2s         1/1     Running   5          45m   192.168.1.94   mc4    <none>           <none>
kube-system   kube-flannel-ds-jvvmp         1/1     Running   5          48m   192.168.1.92   mc2    <none>           <none>
kube-system   kube-flannel-ds-qlvbc         1/1     Running   6          45m   192.168.1.93   mc3    <none>           <none>
kube-system   kube-flannel-ds-ssb9t         1/1     Running   3          77m   192.168.1.91   mc1    <none>           <none>
kube-system   kube-proxy-7t9ff              1/1     Running   2          45m   192.168.1.93   mc3    <none>           <none>
kube-system   kube-proxy-8jhc7              1/1     Running   2          88m   192.168.1.91   mc1    <none>           <none>
kube-system   kube-proxy-cg75m              1/1     Running   2          45m   192.168.1.94   mc4    <none>           <none>
kube-system   kube-proxy-mq8j7              1/1     Running   2          48m   192.168.1.92   mc2    <none>           <none>
kube-system   kube-scheduler-mc1            1/1     Running   5          31m   192.168.1.91   mc1    <none>           <none>

$ docker ps -a # (check the exited and restarted services)

    CONTAINER ID   NAMES                                                                                                    STATUS                            IMAGE                  NETWORKS   PORTS
    0e179c6495db   k8s_kube-apiserver_kube-apiserver-mc1_kube-system_c55114bd57b1bf357c8f4c0d749ae105_13                    Up About a minute                 66eaad223e2c                      
    2ccb014beb73   k8s_kube-scheduler_kube-scheduler-mc1_kube-system_fe362b2b6b08ca576b7416df7f2e7845_6                     Up 3 minutes                      21e17680ca2d                      
    3322f6ec1546   k8s_kube-controller-manager_kube-controller-manager-mc1_kube-system_17cf17caf36ba27e3d2ec4f113a0cf6f_6   Up 3 minutes                      a1ab72ce4ba2                      
    583129da455f   k8s_kube-apiserver_kube-apiserver-mc1_kube-system_c55114bd57b1bf357c8f4c0d749ae105_12                    Exited (137) About a minute ago   66eaad223e2c                      
    72268d8e1503   k8s_install-cni_kube-flannel-ds-ssb9t_kube-system_dbf3513d-dad2-462d-9107-4813acf9c23a_0                 Exited (0) 5 minutes ago          263b01b3ca1f                      
    fe013d07f186   k8s_kube-controller-manager_kube-controller-manager-mc1_kube-system_17cf17caf36ba27e3d2ec4f113a0cf6f_5   Exited (255) 3 minutes ago        a1ab72ce4ba2                      
    34ef8757b63d   k8s_kube-scheduler_kube-scheduler-mc1_kube-system_fe362b2b6b08ca576b7416df7f2e7845_5                     Exited (255) 3 minutes ago        21e17680ca2d                      
    fd8e0c0ba27f   k8s_coredns_coredns-74ff55c5b-8pm9r_kube-system_3b813dc9-827d-4cf6-88cc-027491b350f1_2                   Up 32 minutes                     15c1a66b013b                      
    f44e2c45ed87   k8s_coredns_coredns-74ff55c5b-pxdqz_kube-system_c3b7fbf2-2064-4f3f-b1b2-dec5dad904b7_2                   Up 32 minutes                     15c1a66b013b                      
    04fa4eca1240   k8s_POD_coredns-74ff55c5b-8pm9r_kube-system_3b813dc9-827d-4cf6-88cc-027491b350f1_42                      Up 32 minutes                     k8s.gcr.io/pause:3.2   none       
    f00c36d6de75   k8s_POD_coredns-74ff55c5b-pxdqz_kube-system_c3b7fbf2-2064-4f3f-b1b2-dec5dad904b7_42                      Up 32 minutes                     k8s.gcr.io/pause:3.2   none       
    a1d6814e1b04   k8s_kube-flannel_kube-flannel-ds-ssb9t_kube-system_dbf3513d-dad2-462d-9107-4813acf9c23a_3                Up 32 minutes                     263b01b3ca1f                      
    94b231456ed7   k8s_kube-proxy_kube-proxy-8jhc7_kube-system_cc637e27-3b14-41bd-9f04-c1779e500a3a_2                       Up 33 minutes                     377de0f45e5c                      
    df91856450bd   k8s_POD_kube-flannel-ds-ssb9t_kube-system_dbf3513d-dad2-462d-9107-4813acf9c23a_2                         Up 34 minutes                     k8s.gcr.io/pause:3.2   host       
    b480b844671a   k8s_POD_kube-proxy-8jhc7_kube-system_cc637e27-3b14-41bd-9f04-c1779e500a3a_2                              Up 34 minutes                     k8s.gcr.io/pause:3.2   host       
    1d4a7bcaad38   k8s_etcd_etcd-mc1_kube-system_14b7b6d6446e21cc57f0b40571ae3958_2                                         Up 35 minutes                     2e91dde7e952                      
    e5d517a9c29d   k8s_POD_kube-controller-manager-mc1_kube-system_17cf17caf36ba27e3d2ec4f113a0cf6f_1                       Up 35 minutes                     k8s.gcr.io/pause:3.2   host       
    3a3da7dbf3ad   k8s_POD_kube-apiserver-mc1_kube-system_c55114bd57b1bf357c8f4c0d749ae105_2                                Up 35 minutes                     k8s.gcr.io/pause:3.2   host       
    eef29cdebf5f   k8s_POD_etcd-mc1_kube-system_14b7b6d6446e21cc57f0b40571ae3958_2                                          Up 35 minutes                     k8s.gcr.io/pause:3.2   host       
    3631d43757bc   k8s_POD_kube-scheduler-mc1_kube-system_fe362b2b6b08ca576b7416df7f2e7845_1                                Up 35 minutes                     k8s.gcr.io/pause:3.2   host       

I see no weird issues on the logs (I'm a k8s beginner). This was working until a month ago, when I've reinstalled this for practicing, this is probably my tenth install attempt, I've tried different options, versions and googled a lot, but can't find no solution.

What could be the reason? What else can I try? How can I get to the root of the problem?


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Answer

0 votes
by (71.8m points)
等待大神答复

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...