0
pqy@localhost ~/rancher-205 $ KUBECONFIG=kube_config_cluster.yml kc get endpoints -A
NAMESPACE       NAME                      ENDPOINTS        AGE
default         kubernetes                10.0.2.60:6443   5m49s
ingress-nginx   default-http-backend                       3m50s
kube-system     kube-controller-manager   <none>           5m36s
kube-system     kube-dns                                   4m20s
kube-system     kube-scheduler            <none>           5m24s
kube-system     metrics-server                             4m6s
pqy@localhost ~/rancher-205 $ KUBECONFIG=kube_config_cluster.yml kc get endpoints -A
NAMESPACE       NAME                      ENDPOINTS        AGE
default         kubernetes                10.0.2.60:6443   6m6s
ingress-nginx   default-http-backend      10.97.6.5:8080   4m7s
kube-system     kube-controller-manager   <none>           5m53s
kube-system     kube-dns                                   4m37s
kube-system     kube-scheduler            <none>           5m41s
kube-system     metrics-server                             4m23s
pqy@localhost ~/rancher-205 $ KUBECONFIG=kube_config_cluster.yml kc get endpoints -A
NAMESPACE       NAME                      ENDPOINTS                                  AGE
default         kubernetes                10.0.2.60:6443                             6m15s
ingress-nginx   default-http-backend      10.97.6.5:8080                             4m16s
kube-system     kube-controller-manager   <none>                                     6m2s
kube-system     kube-dns                  10.97.6.2:53,10.97.6.2:53,10.97.6.2:9153   4m46s
kube-system     kube-scheduler            <none>                                     5m50s
kube-system     metrics-server            10.97.6.1:4443                             4m32s
pqy@localhost ~/rancher-205 $ KUBECONFIG=kube_config_cluster.yml kc get endpoints -A
NAMESPACE       NAME                      ENDPOINTS        AGE
default         kubernetes                10.0.2.60:6443   6m27s
ingress-nginx   default-http-backend                       4m28s
kube-system     kube-controller-manager   <none>           6m14s
kube-system     kube-dns                                   4m58s
kube-system     kube-scheduler            <none>           6m2s
kube-system     metrics-server                             4m44s
pqy@localhost ~/rancher-205 $ kc get po -A
The connection to the server localhost:8080 was refused - did you specify the right host or port?
pqy@localhost ~/rancher-205 $ KUBECONFIG=kube_config_cluster.yml kc get po -A
NAMESPACE       NAME                                       READY   STATUS      RESTARTS   AGE
ingress-nginx   default-http-backend-67c77b6989-lt5j2      1/1     Running     0          4m40s
ingress-nginx   nginx-ingress-controller-djfms             1/1     Running     0          4m40s
kube-system     calico-kube-controllers-7dbc97f587-7hfxm   1/1     Running     0          2m43s
kube-system     calico-node-582ww                          1/1     Running     0          2m44s
kube-system     coredns-7787f4598b-qhpx6                   1/1     Running     0          5m11s
kube-system     coredns-autoscaler-b79dfc89b-2ssbg         1/1     Running     0          5m10s
kube-system     metrics-server-756d456b8d-xdrr9            1/1     Running     0          4m56s
kube-system     rke-coredns-addon-deploy-job-9gl2h         0/1     Completed   0          5m21s
kube-system     rke-ingress-controller-deploy-job-gjzpj    0/1     Completed   0          4m50s
kube-system     rke-metrics-addon-deploy-job-vj56b         0/1     Completed   0          5m6s

我只是用 rke 部署了一个新的集群,但我发现了一个奇怪的问题。当完全没有 pod 崩溃时,端点会循环出现/消失。我的 kubernets 版本是 v1.18.20。有任何想法吗??

4

0 回答 0