查看 Node状态
[root@master dashboard]# kubectl get nodesNAME STATUS ROLES AGE VERSIONmaster Ready master 44h v1.16.0node1 Ready <none> 43h v1.16.0node2 Ready <none> 43h v1.16.0[root@master dashboard]# kubectl get node node1 //指定某个资源NAME STATUS ROLES AGE VERSIONnode1 Ready <none> 43h v1.16.0[root@master dashboard]# kubectl get node node1 -o wideNAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIMEnode1 Ready <none> 43h v1.16.0 192.168.81.31 <none> CentOS Linux 7 (Core) 3.10.0-514.el7.x86_64 docker://20.10.17
查看 Service 信息
[root@master dashboard]# kubectl get serviceNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEkubernetes ClusterIP 10.96.0.1 <none> 443/TCP 44h
查看所有名称空间内资源
[root@master dashboard]# kubectl get pods --all-namespacesNAMESPACE NAME READY STATUS RESTARTS AGEkube-flannel kube-flannel-ds-4jrpc 1/1 Running 0 43hkube-flannel kube-flannel-ds-kwjzw 1/1 Running 0 43hkube-flannel kube-flannel-ds-zg8q8 1/1 Running 0 43hkube-system coredns-5644d7b6d9-bs4gj 1/1 Running 0 44hkube-system coredns-5644d7b6d9-xf25l 1/1 Running 0 44hkube-system etcd-master 1/1 Running 0 44hkube-system kube-apiserver-master 1/1 Running 0 23mkube-system kube-controller-manager-master 1/1 Running 5 44hkube-system kube-proxy-48lg7 1/1 Running 0 43hkube-system kube-proxy-hwwth 1/1 Running 0 43hkube-system kube-proxy-mp8tf 1/1 Running 0 44hkube-system kube-scheduler-master 1/1 Running 4 44hkube-system metrics-server-77946ff588-smqbt 0/1 ImagePullBackOff 0 30mkubernetes-dashboard dashboard-metrics-scraper-76585494d8-2czfj 1/1 Running 0 17hkubernetes-dashboard kubernetes-dashboard-5996555fd8-p8qgc 1/1 Running 0 17h或者# kubectl get pods -A
同时查看多种资源信息
[root@master dashboard]# kubectl get svc,pod -n kube-systemNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEservice/kube-dns ClusterIP 10.96.0.10 <none> 53/UDP,53/TCP,9153/TCP 44hservice/metrics-server ClusterIP 10.99.145.57 <none> 443/TCP 32mNAME READY STATUS RESTARTS AGEpod/coredns-5644d7b6d9-bs4gj 1/1 Running 0 44hpod/coredns-5644d7b6d9-xf25l 1/1 Running 0 44hpod/etcd-master 1/1 Running 0 44hpod/kube-apiserver-master 1/1 Running 0 26mpod/kube-controller-manager-master 1/1 Running 5 44hpod/kube-proxy-48lg7 1/1 Running 0 43hpod/kube-proxy-hwwth 1/1 Running 0 43hpod/kube-proxy-mp8tf 1/1 Running 0 44hpod/kube-scheduler-master 1/1 Running 4 44hpod/metrics-server-77946ff588-smqbt 0/1 ImagePullBackOff 0 32m
查看 API 对象细节
使用 kubectl describe 命令,查看一个 API 对象的细节:注意:Events(事件) 值得你特别关注在 Kubernetes 执行的过程中,对 API 对象的所有重要操作,都会被记录在这个对象的 Events 里,并且显示在 kubectl describe 指令返回的结果中。比如,对于这个 Pod,我们可以看到它被创建之后,被调度器调度(Successfully assigned)到了 node-1,拉取了指定的镜像(pulling image),然后启动了 Pod 里定义的容器(Started container)。这个部分正是我们将来进行 Debug 的重要依据。如果有异常发生,一定要第一时间查看这些 Events,往往可以看到非常详细的错误信息。[root@master dashboard]# kubectl describe node node1Name: node1Roles: <none>Labels: beta.kubernetes.io/arch=amd64 beta.kubernetes.io/os=linux kubernetes.io/arch=amd64 kubernetes.io/hostname=node1 kubernetes.io/os=linuxAnnotations: flannel.alpha.coreos.com/backend-data: {"VNI":1,"VtepMAC":"b6:19:ad:57:ef:06"} flannel.alpha.coreos.com/backend-type: vxlan flannel.alpha.coreos.com/kube-subnet-manager: true flannel.alpha.coreos.com/public-ip: 192.168.81.31 kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock node.alpha.kubernetes.io/ttl: 0 volumes.kubernetes.io/controller-managed-attach-detach: trueCreationTimestamp: Tue, 06 Sep 2022 23:15:29 +0800说明:无效但是显示出来的节点可以用delete删除:# kubectl delete node 192.168.245.252node "192.168.245.252" deleted删除pod[root@master dashboard]# kubectl delete pod metrics-server-77946ff588-smqbt -n kube-systempod "metrics-server-77946ff588-smqbt" deletedkubectl delete pod <podname> -n <namespace>
查看集群信息
[root@master dashboard]# kubectl cluster-infoKubernetes master is running at https://192.168.81.30:6443KubeDNS is running at https://192.168.81.30:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxyTo further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
查看各组件信息
使用安全连接:[root@master dashboard]# kubectl -s https://192.168.81.30:6443 get componentstatusesNAME STATUS MESSAGE ERRORcontroller-manager Healthy ok scheduler Healthy ok etcd-0 Healthy {"health":"true"} [root@master dashboard]# kubectl -s https://192.168.81.30:6443 get cs未使用安全连接# kubectl -s http://localhost:8080 get componentstatuses
查看资源类型所对应的Apiversion
[root@master dashboard]# kubectl explain podKIND: PodVERSION: v1
查看帮助
# kubectl explain deployment# kubectl explain deployment.spec# kubectl explain deployment.spec.replicas


