- 已编辑
kubectl get pods --all-namespaces -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system calico-kube-controllers-6f8f7fd457-qt6cj 1/1 Running 0 7h59m 192.168.0.166 master <none> <none>
kube-system calico-node-lgqcb 1/1 Running 0 7h59m 192.168.0.155 node1 <none> <none>
kube-system calico-node-qqjz8 1/1 Running 0 7h59m 192.168.0.144 node2 <none> <none>
kube-system calico-node-tvsfh 1/1 Running 1 7h59m 192.168.0.166 master <none> <none>
kube-system coredns-7f9d8dc6c8-k6dkg 1/1 Running 0 7h59m 10.233.70.1 master <none> <none>
kube-system dns-autoscaler-796f4ddddf-2f8mf 1/1 Running 0 7h59m 10.233.70.2 master <none> <none>
kube-system kube-apiserver-master 1/1 Running 0 8h 192.168.0.166 master <none> <none>
kube-system kube-controller-manager-master 1/1 Running 1 8h 192.168.0.166 master <none> <none>
kube-system kube-proxy-299jd 1/1 Running 0 8h 192.168.0.144 node2 <none> <none>
kube-system kube-proxy-5qjxd 1/1 Running 0 8h 192.168.0.166 master <none> <none>
kube-system kube-proxy-7r9p2 1/1 Running 0 8h 192.168.0.155 node1 <none> <none>
kube-system kube-scheduler-master 1/1 Running 1 8h 192.168.0.166 master <none> <none>
kube-system nodelocaldns-h577n 1/1 Running 0 7h59m 192.168.0.166 master <none> <none>
kube-system nodelocaldns-qnt28 1/1 Running 0 7h59m 192.168.0.155 node1 <none> <none>
kube-system nodelocaldns-sj8tp 1/1 Running 0 7h59m 192.168.0.144 node2 <none> <none>
kube-system openebs-localpv-provisioner-77fbd6858d-gpczv 1/1 Running 2 7h36m 10.233.90.2 node1 <none> <none>
kube-system openebs-ndm-ms2ps 1/1 Running 0 7h36m 192.168.0.155 node1 <none> <none>
kube-system openebs-ndm-n54r5 1/1 Running 0 7h23m 192.168.0.144 node2 <none> <none>
kube-system openebs-ndm-operator-59c75c96fc-4rhwv 1/1 Running 1 7h36m 10.233.90.3 node1 <none> <none>
kube-system tiller-deploy-79b566b5ff-8glxm 1/1 Running 0 7h59m 10.233.90.1 node1 <none> <none>
kubesphere-controls-system default-http-backend-5d464dd566-426kq 1/1 Running 0 7h25m 10.233.90.5 node1 <none> <none>
kubesphere-controls-system kubectl-admin-6c664db975-fbzh8 1/1 Running 0 7h25m 10.233.90.8 node1 <none> <none>
kubesphere-monitoring-system kube-state-metrics-566cdbcb48-jn9ll 4/4 Running 0 7h25m 10.233.90.7 node1 <none> <none>
kubesphere-monitoring-system node-exporter-4gxcq 2/2 Running 0 7h25m 192.168.0.144 node2 <none> <none>
kubesphere-monitoring-system node-exporter-f7b2m 2/2 Running 0 7h25m 192.168.0.166 master <none> <none>
kubesphere-monitoring-system node-exporter-hn9g9 2/2 Running 0 7h25m 192.168.0.155 node1 <none> <none>
kubesphere-monitoring-system prometheus-k8s-0 3/3 Running 1 7h25m 10.233.90.14 node1 <none> <none>
kubesphere-monitoring-system prometheus-k8s-1 3/3 Running 1 7h25m 10.233.90.13 node1 <none> <none>
kubesphere-monitoring-system prometheus-k8s-system-0 3/3 Running 1 7h25m 10.233.90.17 node1 <none> <none>
kubesphere-monitoring-system prometheus-k8s-system-1 3/3 Running 1 7h25m 10.233.90.18 node1 <none> <none>
kubesphere-monitoring-system prometheus-operator-6b97679cfd-kxtm7 1/1 Running 0 7h25m 10.233.90.6 node1 <none> <none>
kubesphere-system ks-account-596657f8c6-c97dv 1/1 Running 0 7h25m 10.233.70.9 master <none> <none>
kubesphere-system ks-apigateway-78bcdc8ffc-9nrnn 1/1 Running 0 7h25m 10.233.70.7 master <none> <none>
kubesphere-system ks-apiserver-5b548d7c5c-v45b2 1/1 Running 0 7h25m 10.233.70.8 master <none> <none>
kubesphere-system ks-console-78bcf96dbf-zqq59 1/1 Running 0 7h25m 10.233.70.11 master <none> <none>
kubesphere-system ks-controller-manager-696986f8d9-sndh2 1/1 Running 1 7h25m 10.233.70.10 master <none> <none>
kubesphere-system ks-installer-7d9fb945c7-dgxg5 1/1 Running 0 7h36m 10.233.90.4 node1 <none> <none>
kubesphere-system openldap-0 1/1 Running 0 7h26m 10.233.70.6 master <none> <none>
kubesphere-system redis-6fd6c6d6f9-pt5d8 1/1 Running 0 7h26m 10.233.70.5 master <none> <none>
pod都是running状态的,但是访问任何节点的30880都是无法访问,这到底是是咋了