页面历史记录

kubectl get pod
# 以下为执行kubectl get pod命令的输出结果
NAME                                      READY   STATUS    RESTARTS   AGE
celery-beat-5fb59494c6-mxn2f              1/1     Running   0          12d
celery-quick-dd7bdc486-cn5pf              1/1     Running   0          12d
celery-slow-67986d56b9-89frc              1/1     Running   0          12d
default-http-backend-7c9558dbb6-pdffv     1/1     Running   7          415d
deploy-server-65d78f8d8b-qb82v            1/1     Running   8          415d
deploy-server-schedule-7dc9fc44dd-kk7l9   1/1     Running   9          415d
elasticsearch-7d7974d7cd-w9frq            1/1     Running   0          157d
hcm-cloud-6b96f8f889-6bc79                1/1     Running   0          12d
hcm-cloud-6b96f8f889-f9smh                1/1     Running   0          12d
hcm-core-7f77d86578-67czb                 1/1     Running   0          12d
hcm-office-5c549c7c7c-gs2zv               1/1     Running   108        554d
hcm-script-7c797b9dc7-pjx7h               1/1     Running   30         12d
nginx-ingress-controller-bkkqs            1/1     Running   9          554d
redis-656865c997-dnxtj                    1/1     Running   7          547d
redis-background-6b68b554b6-ml5qt         1/1     Running   0          148d
redis-monitor-68d449c998-l4l6g            1/1     Running   7          554d
# 根据输出结果，我们需要关注的内容如下
# READY状态是不是 1/1，比如0/1（同时，status 为Running状态）说明服务器启动还没有成功，需要继续等待
# 如果STATUS非Running状态等其他状态，说明服务不可用。请联系部署老师帮忙分析查看
# AGE列为pod的运行时间长度，后面的单位d为day的缩写，也就是天数；刚开始启动运行单位是s代表是秒，然后是m代表是分钟，然后是h代表是小时

kubectl get pod -owide
# 该命令可以查询更详细的信息，比如一个pod是运行在那台服务器上等信息
NAME                                      READY   STATUS    RESTARTS   AGE    IP             NODE            NOMINATED NODE   READINESS GATES
celery-beat-5fb59494c6-mxn2f              1/1     Running   0          12d    172.20.0.234   192.168.100.59   <none>           <none>
celery-quick-dd7bdc486-cn5pf              1/1     Running   0          12d    172.20.0.238   192.168.100.59   <none>           <none>
celery-slow-67986d56b9-89frc              1/1     Running   0          12d    172.20.0.240   192.168.100.59   <none>           <none>
default-http-backend-7c9558dbb6-pdffv     1/1     Running   7          415d   172.20.0.59    192.168.100.59   <none>           <none>
deploy-server-65d78f8d8b-qb82v            1/1     Running   8          415d   172.20.0.71    192.168.100.59   <none>           <none>
deploy-server-schedule-7dc9fc44dd-kk7l9   1/1     Running   9          415d   172.20.0.67    192.168.100.59   <none>           <none>
elasticsearch-7d7974d7cd-w9frq            1/1     Running   0          157d   172.20.0.111   192.168.100.59   <none>           <none>
hcm-cloud-6b96f8f889-6bc79                1/1     Running   0          12d    172.20.0.231   192.168.100.59   <none>           <none>
hcm-cloud-6b96f8f889-f9smh                1/1     Running   0          12d    172.20.0.237   192.168.100.59   <none>           <none>
hcm-core-7f77d86578-67czb                 1/1     Running   0          12d    172.20.0.241   192.168.100.59   <none>           <none>
hcm-office-5c549c7c7c-gs2zv               1/1     Running   108        554d   172.20.0.50    192.168.100.59   <none>           <none>
hcm-script-7c797b9dc7-pjx7h               1/1     Running   30         12d    172.20.0.233   192.168.100.59   <none>           <none>
nginx-ingress-controller-bkkqs            1/1     Running   9          554d   172.20.0.68    192.168.100.59   <none>           <none>
redis-656865c997-dnxtj                    1/1     Running   7          547d   172.20.0.51    192.168.100.59   <none>           <none>
redis-background-6b68b554b6-ml5qt         1/1     Running   0          148d   172.20.0.122   192.168.100.59   <none>           <none>
redis-monitor-68d449c998-l4l6g            1/1     Running   7          554d   172.20.0.66    192.168.100.59   <none>           <none>