kubectl一些命令

最新推荐文章于 2024-07-29 10:13:00 发布

zhixingheyi_tian

最新推荐文章于 2024-07-29 10:13:00 发布

阅读量487

点赞数

分类专栏： kubernetes 云计算

本文链接：https://blog.csdn.net/zhixingheyi_tian/article/details/89145606

版权

云计算同时被 2 个专栏收录

92 篇文章 0 订阅

订阅专栏

kubernetes

35 篇文章 0 订阅

订阅专栏

kubectl get pods --namespace kube-system

[root@bdpe822n2 helmPackage]# kubectl get pods --namespace kube-system
NAME                               READY   STATUS    RESTARTS   AGE
coredns-fb8b8dccf-bq4tl            1/1     Running   1          164m
coredns-fb8b8dccf-q5m2b            1/1     Running   1          164m
etcd-minikube                      1/1     Running   0          163m
kube-addon-manager-minikube        1/1     Running   0          163m
kube-apiserver-minikube            1/1     Running   0          163m
kube-controller-manager-minikube   1/1     Running   0          163m
kube-proxy-6hjtk                   1/1     Running   0          164m
kube-scheduler-minikube            1/1     Running   0          163m
storage-provisioner                1/1     Running   0          164m
tiller-deploy-c48485567-7ndpv      1/1     Running   0          2m16s

kubectl get pods --namespace default

[root@bdpe822n2 helmPackage]# kubectl get pods --namespace default
NAME                                               READY   STATUS      RESTARTS   AGE
spark-pi-2b608f780e8b396492abc330cf6dc2a6-driver   0/1     Completed   0          157m
spark-pi-ba6a0d78f88437738ff357a93b2c4ae1-driver   0/1     Completed   0          140m
spark-pi-d9139d8e335933c7891a817de670193e-driver   0/1     Completed   0          138m
spark-pi-f3a5946156cb3128a579dd0b50e9d528-driver   0/1     Error       0          161m

We can use this command “kubectl get” to list nodes, pods, services and replication controllers. Also can get a list of all the possible resource types by invoking kubectl get without specifying the type. You can then use those types with various kubectl commands like get, describe, etc. The list also shows the abbreviations I mentioned earlier.

show labels

#  kubectl get nodes --show-labels
NAME    STATUS   ROLES    AGE   VERSION   LABELS
sr531   Ready    master   15d   v1.14.1   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=sr531,kubernetes.io/os=linux,node-role.kubernetes.io/master=
sr533   Ready    <none>   27m   v1.14.1   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=sr533,kubernetes.io/os=linux
sr535   Ready    <none>   12d   v1.14.1   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=sr535,kubernetes.io/os=linux

# kubectl describe node sr531
Name:               sr531
Roles:              master
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=sr531
                    kubernetes.io/os=linux
                    node-role.kubernetes.io/master=

kubectl describe

查看某个 pod 状态。
如果有指定的 namespace ，需要加上 -n {namespace}

#kubectl describe pod weave-net-7dcnb -n kube-system
...
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  8m44s                  default-scheduler  Successfully assigned kube-system/weave-net-7dcnb to sr531
  Normal   Pulling    8m43s                  kubelet, sr531     Pulling image "docker.io/weaveworks/weave-kube:2.7.0"
  Normal   Pulled     7m10s                  kubelet, sr531     Successfully pulled image "docker.io/weaveworks/weave-kube:2.7.0"
  Normal   Created    7m10s                  kubelet, sr531     Created container weave
  Normal   Started    7m10s                  kubelet, sr531     Started container weave
  Warning  Failed     5m10s                  kubelet, sr531     Failed to pull image "docker.io/weaveworks/weave-npc:2.7.0": rpc error: code = Unknown desc = context canceled
  Warning  Failed     5m10s                  kubelet, sr531     Error: ImagePullBackOff
  Warning  Failed     5m10s                  kubelet, sr531     Error: ErrImagePull
  Normal   BackOff    5m10s                  kubelet, sr531     Back-off pulling image "docker.io/weaveworks/weave-npc:2.7.0"
  Normal   Pulling    4m59s (x2 over 7m10s)  kubelet, sr531     Pulling image "docker.io/weaveworks/weave-npc:2.7.0"
  Normal   Pulled     2m47s                  kubelet, sr531     Successfully pulled image "docker.io/weaveworks/weave-npc:2.7.0"
  Normal   Created    2m47s                  kubelet, sr531     Created container weave-npc
  Normal   Started    2m47s                  kubelet, sr531     Started container weave-npc

...

list 所有pod 的详细信息

# kubectl get pod  -o wide --all-namespaces
NAMESPACE     NAME                            READY   STATUS    RESTARTS   AGE     IP           NODE    NOMINATED NODE   READINESS GATES
kube-system   coredns-584795fc57-ld7jd        1/1     Running   0          4h56m   10.32.0.3    sr531   <none>           <none>
kube-system   coredns-584795fc57-xthtk        1/1     Running   0          4h56m   10.32.0.2    sr531   <none>           <none>
kube-system   etcd-sr531                      1/1     Running   0          4h55m   10.1.2.131   sr531   <none>           <none>
kube-system   kube-apiserver-sr531            1/1     Running   0          4h54m   10.1.2.131   sr531   <none>           <none>
kube-system   kube-controller-manager-sr531   1/1     Running   0          4h55m   10.1.2.131   sr531   <none>           <none>
kube-system   kube-proxy-9w4cc                0/1     Pending   0          4h32m   <none>       sr535   <none>           <none>
kube-system   kube-proxy-ph76w                1/1     Running   0          4h56m   10.1.2.131   sr531   <none>           <none>
kube-system   kube-scheduler-sr531            1/1     Running   0          4h55m   10.1.2.131   sr531   <none>           <none>
kube-system   weave-net-7dcnb                 2/2     Running   0          4h25m   10.1.2.131   sr531   <none>           <none>
kube-system   weave-net-l8fqj                 0/2     Pending   0          4h25m   <none>       sr535   <none>           <none>

READY 数字含义：It shows how many containers in a pod are considered ready.

删除某个节点

# kubectl delete node sr535
node "sr535" deleted

查看一个pod里某个container

# kubectl logs -f  weave-net-gzr79  -n kube-system
error: a container name must be specified for pod weave-net-gzr79, choose one of: [weave weave-npc]
# kubectl logs -f  weave-net-gzr79  -n kube-system -c weave
INFO: 2020/12/24 03:37:24.213596 Command line options: map[conn-limit:200 datapath:datapath db-prefix:/weavedb/weave-net docker-api: expect-npc:true host-root:/host http-addr:127.0.0.1:6784 ipalloc-init:consensus=1 ipalloc-range:10.32.0.0/12 metrics-addr:0.0.0.0:6782 name:5e:e9:dc:6d:48:f1 nickname:vsr266 no-dns:true no-masq-local:true port:6783]
INFO: 2020/12/24 03:37:24.213670 weave  2.7.0
INFO: 2020/12/24 03:37:24.455742 Bridge type is bridged_fastdp
INFO: 2020/12/24 03:37:24.455792 Communication between peers is unencrypted.
INFO: 2020/12/24 03:37:24.460892 Our name is 5e:e9:dc:6d:48:f1(vsr266)
INFO: 2020/12/24 03:37:24.460975 Launch detected - using supplied peer list: [10.0.0.160]

zhixingheyi_tian

关注

0
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
kubectl一些命令

kubectl get pods --namespace kube-system[root@bdpe822n2 helmPackage]# kubectl get pods --namespace kube-systemNAME READY STATUS RESTARTS AGEcoredns-fb8b8dccf-bq...
复制链接

扫一扫

专栏目录