hongming [root@paas01 ~]# kubectl get pods -n kubesphere-system
NAME READY STATUS RESTARTS AGE
etcd-5769d4997f-bmdvj 1/1 Running 0 5d22h
ks-account-84695f7c9d-4vdkf 1/2 CrashLoopBackOff 283 23h
ks-account-84695f7c9d-q8mzm 1/2 CrashLoopBackOff 276 23h
ks-account-9ffb94b99-5gmng 1/1 Running 0 5d22h
ks-account-9ffb94b99-wtthr 1/1 Running 0 5d22h
ks-apigateway-d899b7b98-48gzs 1/1 Running 0 5d22h
ks-apigateway-d899b7b98-r2d4c 1/1 Running 0 41h
ks-apigateway-d899b7b98-vrxzc 1/1 Running 1 41h
ks-apiserver-5c5759c866-ctsrb 1/1 Running 4 41h
ks-apiserver-5c5759c866-hjkpl 1/1 Running 4 41h
ks-apiserver-5c5759c866-m6bwm 1/1 Running 0 5d22h
ks-console-97cf4db85-9jhkz 1/1 Running 0 5d22h
ks-console-97cf4db85-h7qzp 1/1 Running 0 5d22h
ks-console-97cf4db85-wgcn6 1/1 Running 0 5d22h
ks-controller-manager-9dcc6599f-99sgk 1/1 Running 0 5d22h
ks-controller-manager-9dcc6599f-bch4w 1/1 Running 1 5d22h
ks-controller-manager-9dcc6599f-hdqtc 1/1 Running 0 5d22h
ks-installer-7d9fb945c7-gpj2d 1/1 Running 0 5d23h
minio-845b7bd867-qvqmm 1/1 Running 1 5d23h
mysql-66df969d-4lxff 1/1 Running 0 5d22h
openldap-0 1/1 Running 0 5d23h
openldap-1 1/1 Running 0 5d22h
redis-ha-haproxy-ffb8d889d-9rlwv 1/1 Running 0 5d23h
redis-ha-haproxy-ffb8d889d-g5jzh 1/1 Running 0 5d23h
redis-ha-haproxy-ffb8d889d-pn6qx 1/1 Running 0 5d23h
redis-ha-server-0 2/2 Running 0 5d23h
redis-ha-server-1 2/2 Running 0 5d23h
redis-ha-server-2 2/2 Running 0 5d23h
[root@paas01 ~]# kubectl get deployment -n kubesphere-system
NAME READY UP-TO-DATE AVAILABLE AGE
etcd 1/1 1 1 5d22h
ks-account 2/3 2 2 5d22h
ks-apigateway 3/3 3 3 5d22h
ks-apiserver 3/3 3 3 5d22h
ks-console 3/3 3 3 5d22h
ks-controller-manager 3/3 3 3 5d22h
ks-installer 1/1 1 1 5d23h
minio 1/1 1 1 5d23h
mysql 1/1 1 1 5d22h
redis-ha-haproxy 3/3 3 3 5d23h
相关查询如下
[root@paas01 ~]# kubectl -n kubesphere-system logs ks-account-84695f7c9d-4vdkf -c ks-account
W0315 06:57:55.215708 1 client_config.go:549] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
I0315 06:57:55.893499 1 server.go:113] Server listening on 0.0.0.0:9090
[root@paas01 ~]# kubectl -n kubesphere-system logs ks-account-84695f7c9d-4vdkf -c ks-account -p
Error from server (BadRequest): previous terminated container "ks-account" in pod "ks-account-84695f7c9d-4vdkf" not found
[root@paas01 ~]# kubectl -n kubesphere-system logs ks-account-84695f7c9d-q8mzm -c ks-account
W0315 07:35:56.276173 1 client_config.go:549] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
I0315 07:35:56.914237 1 server.go:113] Server listening on 0.0.0.0:9090
[root@paas01 ~]# kubectl -n kubesphere-system logs ks-account-84695f7c9d-q8mzm -c ks-account -p
Error from server (BadRequest): previous terminated container "ks-account" in pod "ks-account-84695f7c9d-q8mzm" not found
[root@paas01 ~]# kubectl -n kubesphere-system logs ks-account-9ffb94b99-5gmng -c ks-account
W0310 07:51:51.680599 1 client_config.go:549] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
I0310 07:51:52.322949 1 server.go:113] Server listening on 0.0.0.0:9090
[root@paas01 ~]# kubectl -n kubesphere-system logs ks-account-9ffb94b99-5gmng -c ks-account -p
Error from server (BadRequest): previous terminated container "ks-account" in pod "ks-account-9ffb94b99-5gmng" not found
[root@paas01 ~]# kubectl -n kubesphere-system logs ks-account-9ffb94b99-wtthr -c ks-account
W0310 07:51:07.242536 1 client_config.go:549] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
I0310 07:51:07.873259 1 server.go:113] Server listening on 0.0.0.0:9090
[root@paas01 ~]# @
