devbox
花生_TL007
这个屌丝很懒，什么也没留下！
关注作者
热门标签
热门文章
当前位置:   article > 正文

使用kubectl管理Kubernetes(k8s)集群：常用命令，查看负载，命名空间namespace管理_kubectl get node 查看负载

作者：花生_TL007 | 2024-03-20 23:06:18

赞

踩

kubectl get node 查看负载

目录

一.系统环境

服务器版本docker软件版本CPU架构
CentOS Linux release 7.4.1708 (Core)Docker version 20.10.12x86_64

二.前言

kubectl是Kubernetes提供的命令行工具，kubectl 使用 Kubernetes API 与 Kubernetes 集群的控制面进行通信。

针对配置信息，kubectl 在 $HOME/.kube 目录中查找一个名为 config 的配置文件来连接Kubernetes 集群。 你可以通过设置 KUBECONFIG 环境变量或设置 --kubeconfig 参数来指定其它 kubeconfig 文件。

使用kubectl命令行工具的前提是已经有一套可以正常运行的Kubernetes集群，关于Kubernetes(k8s)集群的安装部署，可以查看博客《Centos7 安装部署Kubernetes(k8s)集群》Centos7 安装部署Kubernetes(k8s)集群 - 人生的哲理 - 博客园

三.kubectl

3.1 kubectl语法

kubectl的语法为：kubectl [command] [TYPE] [NAME] [flags]，其中 command、TYPE、NAME 和 flags 分别是：

  • command：指定要对一个或多个资源执行的操作，例如 create、get、describe、delete。

  • TYPE：指定资源类型。资源类型不区分大小写， 可以指定单数、复数或缩写形式。例如，以下命令输出相同的结果：

    1. kubectl get pod pod1
    2. kubectl get pods pod1
    3. kubectl get po pod1

  • NAME：指定资源的名称。名称区分大小写。 如果省略名称，则显示所有资源的详细信息。例如：kubectl get pods。

  • flags： 指定可选的参数。例如，可以使用 -s 或 --server 参数指定 Kubernetes API 服务器的地址和端口。

要对所有类型相同的资源进行分组，请执行以下操作：TYPE1 name1 name2 name<#>。
例子：kubectl get pod example-pod1 example-pod2

分别指定多个资源类型：TYPE1/name1 TYPE1/name2 TYPE2/name3 TYPE<#>/name<#>。
例子：kubectl get pod/example-pod1 replicationcontroller/example-rc1

3.2 kubectl格式化输出

kubectl格式化输出语法：kubectl [command] [TYPE] [NAME] -o <output_format>

输出格式描述
-o custom-columns=spec使用逗号分隔的自定义列列表打印表。
-o custom-columns-file=filename使用 filename文件中的自定义列模板打印表。
-o json输出 JSON 格式的 API 对象
-o jsonpath=template打印 jsonpath 表达式定义的字段
-o jsonpath-file=filename打印 filename>文件中 jsonpath 表达式定义的字段。
-o name仅打印资源名称而不打印任何其他内容。
-o wide以纯文本格式输出，包含所有附加信息。对于 Pod 包含节点名。
-o yaml输出 YAML 格式的 API 对象。

四.kubectl常用命令

查看从什么地址能访问k8s API，会显示k8s集群的master节点的地址

  1. [root@k8scloude1 ~]# kubectl cluster-info 
  2. Kubernetes control plane is running at https://192.168.110.130:6443
  3. CoreDNS is running at https://192.168.110.130:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
  4.  
  5. To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

查看kubectl版本

  1. [root@k8scloude1 ~]# kubectl version 
  2. Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T16:31:21Z", GoVersion:"go1.16.1", Compiler:"gc", Platform:"linux/amd64"}
  3. Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T16:25:06Z", GoVersion:"go1.16.1", Compiler:"gc", Platform:"linux/amd64"}
  4.  
  5. [root@k8scloude1 ~]# kubectl version --short
  6. Client Version: v1.21.0
  7. Server Version: v1.21.0

查看k8s的pod网段，可以看到pod网段为10.244.0.0/16

  1. #查看初始化时候的k8s集群配置:kubeadm config view
  2. [root@k8scloude1 ~]# kubeadm config view
  3. Command "view" is deprecated, This command is deprecated and will be removed in a future release, please use 'kubectl get cm -o yaml -n kube-system kubeadm-config' to get the kubeadm config directly.
  4. apiServer:
  5.   extraArgs:
  6.     authorization-mode: Node,RBAC
  7.   timeoutForControlPlane: 4m0s
  8. apiVersion: kubeadm.k8s.io/v1beta2
  9. certificatesDir: /etc/kubernetes/pki
  10. clusterName: kubernetes
  11. controllerManager: {}
  12. dns:
  13.   type: CoreDNS
  14. etcd:
  15.   local:
  16.     dataDir: /var/lib/etcd
  17. imageRepository: registry.aliyuncs.com/google_containers
  18. kind: ClusterConfiguration
  19. kubernetesVersion: v1.21.0
  20. networking:
  21.   dnsDomain: cluster.local
  22.   podSubnet: 10.244.0.0/16
  23.   serviceSubnet: 10.96.0.0/12
  24. scheduler: {}

查看kubeconfig文件的结构

  1. [root@k8scloude1 ~]# kubectl config view
  2. apiVersion: v1
  3. clusters:
  4. - cluster:
  5.     certificate-authority-data: DATA+OMITTED
  6.     server: https://192.168.110.130:6443
  7.   name: kubernetes
  8. contexts:
  9. - context:
  10.     cluster: kubernetes
  11.     user: kubernetes-admin
  12.   name: kubernetes-admin@kubernetes
  13. current-context: kubernetes-admin@kubernetes
  14. kind: Config
  15. preferences: {}
  16. users:
  17. - name: kubernetes-admin
  18.   user:
  19.     client-certificate-data: REDACTED
  20.     client-key-data: REDACTED
  21.

五.查看kubernetes集群node节点和pod负载

5.1 安装metric-server

查看node节点和pod的负载，发现看不了node和pod的负载，是因为没有安装metric-server

  1. [root@k8scloude1 ~]# kubectl top nodes
  2. W0109 16:45:38.197980   75467 top_node.go:119] Using json format to get metrics. Next release will switch to protocol-buffers, switch early by passing --use-protocol-buffers flag
  3. error: Metrics API not available
  4.  
  5. [root@k8scloude1 ~]# kubectl top pods
  6. W0109 16:45:58.436117   75718 top_pod.go:140] Using json format to get metrics. Next release will switch to protocol-buffers, switch early by passing --use-protocol-buffers flag
  7. error: Metrics API not available

为了查看节点和pod的负载，下面开始安装metric-server

创建目录，用来存放metric-server

  1. [root@k8scloude1 ~]# mkdir metric-server
  2.  
  3. [root@k8scloude1 ~]# cd metric-server/

下载metrics-server并解压

  1. [root@k8scloude1 metric-server]# wget https://github.com/kubernetes-sigs/metrics-server/archive/v0.3.6.tar.gz
  2.  
  3. [root@k8scloude1 metric-server]# ls
  4. v0.3.6.tar.gz
  5.  
  6. [root@k8scloude1 metric-server]# tar xf v0.3.6.tar.gz 
  7.  
  8. [root@k8scloude1 metric-server]# ls
  9. metrics-server-0.3.6  v0.3.6.tar.gz
  10.  
  11. [root@k8scloude1 metric-server]# cd metrics-server-0.3.6/
  12.  
  13. [root@k8scloude1 metrics-server-0.3.6]# ls
  14. cmd  code-of-conduct.md  CONTRIBUTING.md  deploy  Gopkg.lock  Gopkg.toml  hack  LICENSE  Makefile  OWNERS  OWNERS_ALIASES  pkg  README.md  SECURITY_CONTACTS  vendor  version
  15.  
  16. [root@k8scloude1 metrics-server-0.3.6]# cd deploy/
  17.  
  18. [root@k8scloude1 deploy]# ls
  19. 1.7  1.8+  docker  minikube
  20.  
  21. [root@k8scloude1 deploy]# cd 1.8+
  22.  
  23. [root@k8scloude1 1.8+]# ls
  24. aggregated-metrics-reader.yaml  auth-delegator.yaml  auth-reader.yaml  metrics-apiservice.yaml  metrics-server-deployment.yaml  metrics-server-service.yaml  resource-reader.yaml

查看需要下载的镜像，image: k8s.gcr.io/metrics-server-amd64:v0.3.6这个镜像国内访问不了，我们手动下载一个国内镜像

  1. [root@k8scloude1 1.8+]# grep image metrics-server-deployment.yaml
  2.       # mount in tmp so we can safely use from-scratch images and/or read-only containers
  3.         image: k8s.gcr.io/metrics-server-amd64:v0.3.6
  4.         imagePullPolicy: Always

在k8s集群master节点和worker节点都需要下载metrics-server-amd64:v0.3.6镜像

  1. [root@k8scloude1 1.8+]# docker pull mirrorgooglecontainers/metrics-server-amd64:v0.3.6
  2.  
  3. [root@k8scloude1 1.8+]# docker images | grep mirrorgooglecontainers
  4. REPOSITORY                                                        TAG        IMAGE ID       CREATED         SIZE
  5. mirrorgooglecontainers/metrics-server-amd64                       v0.3.6     9dd718864ce6   2 years ago     39.9MB

镜像已经下好了，现在进行docker tag重命名，并删除原镜像mirrorgooglecontainers/metrics-server-amd64:v0.3.6

  1. [root@k8scloude1 1.8+]# docker tag mirrorgooglecontainers/metrics-server-amd64:v0.3.6 k8s.gcr.io/metrics-server-amd64:v0.3.6
  2.  
  3. [root@k8scloude1 1.8+]# docker rmi mirrorgooglecontainers/metrics-server-amd64:v0.3.6

worker节点也进行相同操作

  1. [root@k8scloude2 ~]# docker pull mirrorgooglecontainers/metrics-server-amd64:v0.3.6
  2.  
  3. [root@k8scloude2 ~]# docker tag mirrorgooglecontainers/metrics-server-amd64:v0.3.6 k8s.gcr.io/metrics-server-amd64:v0.3.6
  4.  
  5. [root@k8scloude2 ~]# docker rmi mirrorgooglecontainers/metrics-server-amd64:v0.3.6
  6.  
  7. [root@k8scloude3 ~]# docker pull mirrorgooglecontainers/metrics-server-amd64:v0.3.6
  8.  
  9. [root@k8scloude3 ~]# docker tag mirrorgooglecontainers/metrics-server-amd64:v0.3.6 k8s.gcr.io/metrics-server-amd64:v0.3.6
  10.  
  11. [root@k8scloude3 ~]# docker rmi mirrorgooglecontainers/metrics-server-amd64:v0.3.6

修改配置文件，镜像下载策略imagePullPolicy改为IfNotPresent，IfNotPresent表示只有当镜像在本地不存在时才会拉取

  1. [root@k8scloude1 1.8+]# pwd
  2. /root/metric-server/metrics-server-0.3.6/deploy/1.8+
  3.  
  4. #修改内容如下： imagePullPolicy: IfNotPresent
  5. #        command:
  6. #      - /metrics-server
  7. #        - --metric-resolution=30s
  8. #        - --kubelet-insecure-tls
  9. #        - --kubelet-preferred-address-types=InternalIP
  10. [root@k8scloude1 1.8+]# tail -20 metrics-server-deployment.yaml
  11.         k8s-app: metrics-server
  12.     spec:
  13.       serviceAccountName: metrics-server
  14.       volumes:
  15.       # mount in tmp so we can safely use from-scratch images and/or read-only containers
  16.       - name: tmp-dir
  17.         emptyDir: {}
  18.       containers:
  19.       - name: metrics-server
  20.         image: k8s.gcr.io/metrics-server-amd64:v0.3.6
  21.         imagePullPolicy: IfNotPresent
  22.         command:
  23.         - /metrics-server
  24.         - --metric-resolution=30s
  25.         - --kubelet-insecure-tls
  26.         - --kubelet-preferred-address-types=InternalIP
  27.         volumeMounts:
  28.         - name: tmp-dir
  29.           mountPath: /tmp

安装metrics-server

  1. #kubectl apply -f .    .表示安装当前目录下的所有文件
  2. [root@k8scloude1 1.8+]# kubectl apply -f .
  3. clusterrole.rbac.authorization.k8s.io/system:aggregated-metrics-reader created
  4. Warning: rbac.authorization.k8s.io/v1beta1 ClusterRoleBinding is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRoleBinding
  5. clusterrolebinding.rbac.authorization.k8s.io/metrics-server:system:auth-delegator created
  6. Warning: rbac.authorization.k8s.io/v1beta1 RoleBinding is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 RoleBinding
  7. rolebinding.rbac.authorization.k8s.io/metrics-server-auth-reader created
  8. Warning: apiregistration.k8s.io/v1beta1 APIService is deprecated in v1.19+, unavailable in v1.22+; use apiregistration.k8s.io/v1 APIService
  9. apiservice.apiregistration.k8s.io/v1beta1.metrics.k8s.io created
  10. serviceaccount/metrics-server created
  11. deployment.apps/metrics-server created
  12. service/metrics-server created
  13. clusterrole.rbac.authorization.k8s.io/system:metrics-server created
  14. clusterrolebinding.rbac.authorization.k8s.io/system:metrics-server created

查看所有的命名空间

  1. [root@k8scloude1 1.8+]# kubectl get ns
  2. NAME              STATUS   AGE
  3. default           Active   18h
  4. kube-node-lease   Active   18h
  5. kube-public       Active   18h
  6. kube-system       Active   18h

当观察到metrics-server-bcfb98c76-k5dmj状态为Running，metrics-server服务就正常启动了

  1. [root@k8scloude1 1.8+]# kubectl get pod -n kube-system -o wide
  2. NAME                                       READY   STATUS    RESTARTS   AGE   IP                NODE         NOMINATED NODE   READINESS GATES
  3. calico-kube-controllers-6b9fbfff44-4jzkj   1/1     Running   2          19h   10.244.251.194    k8scloude3   <none>           <none>
  4. calico-node-bdlgm                          1/1     Running   1          19h   192.168.110.130   k8scloude1   <none>           <none>
  5. calico-node-hx8bk                          1/1     Running   1          19h   192.168.110.128   k8scloude3   <none>           <none>
  6. calico-node-nsbfs                          1/1     Running   1          19h   192.168.110.129   k8scloude2   <none>           <none>
  7. coredns-545d6fc579-7wm95                   1/1     Running   1          19h   10.244.158.68     k8scloude1   <none>           <none>
  8. coredns-545d6fc579-87q8j                   1/1     Running   1          19h   10.244.158.67     k8scloude1   <none>           <none>
  9. etcd-k8scloude1                            1/1     Running   1          19h   192.168.110.130   k8scloude1   <none>           <none>
  10. kube-apiserver-k8scloude1                  1/1     Running   1          19h   192.168.110.130   k8scloude1   <none>           <none>
  11. kube-controller-manager-k8scloude1         1/1     Running   1          19h   192.168.110.130   k8scloude1   <none>           <none>
  12. kube-proxy-599xh                           1/1     Running   1          19h   192.168.110.128   k8scloude3   <none>           <none>
  13. kube-proxy-lpj8z                           1/1     Running   1          19h   192.168.110.129   k8scloude2   <none>           <none>
  14. kube-proxy-zxlk9                           1/1     Running   1          19h   192.168.110.130   k8scloude1   <none>           <none>
  15. kube-scheduler-k8scloude1                  1/1     Running   1          19h   192.168.110.130   k8scloude1   <none>           <none>
  16. metrics-server-bcfb98c76-k5dmj             1/1     Running   0          70s   10.244.112.131    k8scloude2   <none>           <none>

5.2 查看node负载

查看node的负载

  1. [root@k8scloude1 1.8+]# kubectl top node 
  2. W0110 11:37:47.025099   75026 top_node.go:119] Using json format to get metrics. Next release will switch to protocol-buffers, switch early by passing --use-protocol-buffers flag
  3. NAME         CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%   
  4. k8scloude1   257m         12%    1487Mi          45%       
  5. k8scloude2   104m         5%     698Mi           36%       
  6. k8scloude3   102m         5%     701Mi           36%

5.3 查看pod负载

查看pod的负载

注释：一核心分成1000个微核心m 1核=1000m

  1. [root@k8scloude1 1.8+]# kubectl top pods
  2. W0110 11:38:40.576780   75696 top_pod.go:140] Using json format to get metrics. Next release will switch to protocol-buffers, switch early by passing --use-protocol-buffers flag
  3. No resources found in default namespace.
  4.  
  5. #-A表示所有命名空间
  6. [root@k8scloude1 1.8+]# kubectl top pods -A
  7. W0110 11:38:47.276962   75784 top_pod.go:140] Using json format to get metrics. Next release will switch to protocol-buffers, switch early by passing --use-protocol-buffers flag
  8. NAMESPACE     NAME                                       CPU(cores)   MEMORY(bytes)   
  9. kube-system   calico-kube-controllers-6b9fbfff44-4jzkj   2m           25Mi            
  10. kube-system   calico-node-bdlgm                          37m          170Mi           
  11. kube-system   calico-node-hx8bk                          43m          157Mi           
  12. kube-system   calico-node-nsbfs                          56m          164Mi           
  13. kube-system   coredns-545d6fc579-7wm95                   3m           18Mi            
  14. kube-system   coredns-545d6fc579-87q8j                   3m           18Mi            
  15. kube-system   etcd-k8scloude1                            14m          91Mi            
  16. kube-system   kube-apiserver-k8scloude1                  60m          351Mi           
  17. kube-system   kube-controller-manager-k8scloude1         21m          56Mi            
  18. kube-system   kube-proxy-599xh                           1m           24Mi            
  19. kube-system   kube-proxy-lpj8z                           1m           24Mi            
  20. kube-system   kube-proxy-zxlk9                           1m           24Mi            
  21. kube-system   kube-scheduler-k8scloude1                  3m           23Mi            
  22. kube-system   metrics-server-bcfb98c76-k5dmj             1m           13Mi

六.命名空间namespace的管理

6.1 何为命名空间namespace

在 Kubernetes 中，命名空间（Namespace） 提供一种机制，将同一集群中的资源划分为相互隔离的组。 同一命名空间内的资源名称要唯一，但跨命名空间时没有这个要求。 命名空间作用域仅针对带有命名空间的对象，例如 Deployment、Service 等， 这种作用域对集群访问的对象不适用，例如 StorageClass、Node、PersistentVolume 等。

6.2 管理命名空间namespace

查看所有的命名空间

  1. [root@k8scloude1 1.8+]# kubectl get namespaces 
  2. NAME              STATUS   AGE
  3. default           Active   19h
  4. kube-node-lease   Active   19h
  5. kube-public       Active   19h
  6. kube-system       Active   19h
  7.  
  8. [root@k8scloude1 1.8+]# kubectl get ns
  9. NAME              STATUS   AGE
  10. default           Active   19h
  11. kube-node-lease   Active   19h
  12. kube-public       Active   19h
  13. kube-system       Active   19h

创建命名空间，注意：不同的namespace之间相互隔离

  1. [root@k8scloude1 1.8+]# kubectl create ns ns1
  2. namespace/ns1 created
  3.  
  4. [root@k8scloude1 1.8+]# kubectl create ns ns2
  5. namespace/ns2 created
  6.  
  7. [root@k8scloude1 1.8+]# kubectl get ns
  8. NAME              STATUS   AGE
  9. default           Active   19h
  10. kube-node-lease   Active   19h
  11. kube-public       Active   19h
  12. kube-system       Active   19h
  13. ns1               Active   6s
  14. ns2               Active   4s

获取全局上下文，可以看到当前命名空间为default

  1. [root@k8scloude1 ~]# kubectl config get-contexts 
  2. CURRENT   NAME                          CLUSTER      AUTHINFO           NAMESPACE
  3. *         kubernetes-admin@kubernetes   kubernetes   kubernetes-admin   default

切换命名空间

  1. #切换命名空间
  2. [root@k8scloude1 ~]# kubectl config set-context --current --namespace=kube-system
  3. Context "kubernetes-admin@kubernetes" modified.
  4.  
  5. [root@k8scloude1 ~]# kubectl config get-contexts 
  6. CURRENT   NAME                          CLUSTER      AUTHINFO           NAMESPACE
  7. *         kubernetes-admin@kubernetes   kubernetes   kubernetes-admin   kube-system
  8.  
  9. #获取当前K8S上下文
  10. [root@k8scloude1 ~]# kubectl config current-context 
  11. kubernetes-admin@kubernetes

6.2 使用kubens管理命名空间namespace

默认的切换命名空间的命令不好用，可以使用第三方的命名空间切换工具：kubens，kubens命令所在的网站为：https://github.com/ahmetb/kubectx/releases/

下载kubens，并授予可执行权限

  1. [root@k8scloude1 ~]# wget https://github.com/ahmetb/kubectx/releases/download/v0.9.4/kubens
  2.  
  3. [root@k8scloude1 ~]# ll -h kubens 
  4. -rw-r--r-- 1 root root 5.5K 12月  8 15:46 kubens
  5.  
  6. [root@k8scloude1 ~]# chmod +x kubens 
  7.  
  8. [root@k8scloude1 ~]# mv kubens /bin/
  9.  
  10. [root@k8scloude1 ~]# ls /bin/kubens 
  11. /bin/kubens

查看所有的命名空间

  1. [root@k8scloude1 ~]# kubens 
  2. default
  3. kube-node-lease
  4. kube-public
  5. kube-system
  6. ns1
  7. ns2

切换namespace

  1. #切换namespace到kube-system
  2. [root@k8scloude1 ~]# kubens kube-system
  3. Context "kubernetes-admin@kubernetes" modified.
  4. Active namespace is "kube-system".
  5.  
  6. #此时，默认查询的就是kube-system命名空间下的pod
  7. [root@k8scloude1 ~]# kubectl get pods -o wide
  8. NAME                                       READY   STATUS    RESTARTS   AGE   IP                NODE         NOMINATED NODE   READINESS GATES
  9. calico-kube-controllers-6b9fbfff44-4jzkj   1/1     Running   2          20h   10.244.251.194    k8scloude3   <none>           <none>
  10. calico-node-bdlgm                          1/1     Running   1          20h   192.168.110.130   k8scloude1   <none>           <none>
  11. calico-node-hx8bk                          1/1     Running   1          20h   192.168.110.128   k8scloude3   <none>           <none>
  12. calico-node-nsbfs                          1/1     Running   1          20h   192.168.110.129   k8scloude2   <none>           <none>
  13. coredns-545d6fc579-7wm95                   1/1     Running   1          20h   10.244.158.68     k8scloude1   <none>           <none>
  14. coredns-545d6fc579-87q8j                   1/1     Running   1          20h   10.244.158.67     k8scloude1   <none>           <none>
  15. etcd-k8scloude1                            1/1     Running   1          20h   192.168.110.130   k8scloude1   <none>           <none>
  16. kube-apiserver-k8scloude1                  1/1     Running   1          20h   192.168.110.130   k8scloude1   <none>           <none>
  17. kube-controller-manager-k8scloude1         1/1     Running   1          20h   192.168.110.130   k8scloude1   <none>           <none>
  18. kube-proxy-599xh                           1/1     Running   1          20h   192.168.110.128   k8scloude3   <none>           <none>
  19. kube-proxy-lpj8z                           1/1     Running   1          20h   192.168.110.129   k8scloude2   <none>           <none>
  20. kube-proxy-zxlk9                           1/1     Running   1          20h   192.168.110.130   k8scloude1   <none>           <none>
  21. kube-scheduler-k8scloude1                  1/1     Running   1          20h   192.168.110.130   k8scloude1   <none>           <none>
  22. metrics-server-bcfb98c76-k5dmj             1/1     Running   0          56m   10.244.112.131    k8scloude2   <none>           <none>

切换namespace到default

  1. #切换namespace到default
  2. [root@k8scloude1 ~]# kubens default
  3. Context "kubernetes-admin@kubernetes" modified.
  4. Active namespace is "default".
  5.  
  6. #此时，默认查询的就是default命名空间下的pod
  7. [root@k8scloude1 ~]# kubectl get pods -o wide
  8. No resources found in default namespace.
  9.  
  10. #要查询kube-public命名空间下的pod，使用-n kube-public指定
  11. [root@k8scloude1 ~]# kubectl get pods -n kube-public
  12. No resources found in kube-public namespace.

致力于一条龙式的为您解决问题

转载至https://www.cnblogs.com/renshengdezheli/p/16693557.html

声明：本文内容由网友自发贡献，不代表【wpsshop博客】立场，版权归原作者所有，本站不承担相应法律责任。如您发现有侵权的内容，请联系我们。转载请注明出处：https://www.wpsshop.cn/w/花生_TL007/article/detail/276614
推荐阅读
相关标签

Copyright © 2003-2013 www.wpsshop.cn 版权所有，并保留所有权利。

  

闽ICP备14008679号