对比有无-o wide参数的区别

kubectl get pod --all-namespaces
kubectl get pod --all-namespaces -o wide
如下，查看所有Pod信息，加上-o wide参数，能看到每个Pod的ip和k8s节点等信息，看的多了

  1. [machangwei@mcw7 ~]$ kubectl get pod --all-namespaces
  2. NAMESPACE     NAME                           READY   STATUS             RESTARTS        AGE
  3. kube-system   coredns-6d8c4cb4d-2296m        1/1     Running            1 (4h52m ago)   8h
  4. kube-system   coredns-6d8c4cb4d-lphb2        1/1     Running            1 (4h52m ago)   8h
  5. kube-system   etcd-mcw7                      1/1     Running            3               8h
  6. kube-system   kube-apiserver-mcw7            1/1     Running            2               8h
  7. kube-system   kube-controller-manager-mcw7   1/1     Running            4 (4h53m ago)   8h
  8. kube-system   kube-flannel-ds-5pxmj          0/1     CrashLoopBackOff   49 (59s ago)    3h51m
  9. kube-system   kube-flannel-ds-8gzfq          1/1     Running            0               4h57m
  10. kube-system   kube-flannel-ds-s4qmj          0/1     CrashLoopBackOff   42 (80s ago)    3h14m
  11. kube-system   kube-proxy-4lmsx               1/1     Running            0               3h51m
  12. kube-system   kube-proxy-c5zmm               1/1     Running            0               8h
  13. kube-system   kube-proxy-npmtv               1/1     Running            0               3h14m
  14. kube-system   kube-scheduler-mcw7            1/1     Running            3 (4h53m ago)   8h
  15. [machangwei@mcw7 ~]$
  16. [machangwei@mcw7 ~]$
  17. [machangwei@mcw7 ~]$ kubectl get pod --all-namespaces -o wide
  18. NAMESPACE     NAME                           READY   STATUS             RESTARTS         AGE     IP           NODE   NOMINATED NODE   READINESS GATES
  19. kube-system   coredns-6d8c4cb4d-2296m        1/1     Running            1 (4h59m ago)    8h      10.244.0.3   mcw7   <none>           <none>
  20. kube-system   coredns-6d8c4cb4d-lphb2        1/1     Running            1 (4h59m ago)    8h      10.244.0.2   mcw7   <none>           <none>
  21. kube-system   etcd-mcw7                      1/1     Running            3                8h      10.0.0.137   mcw7   <none>           <none>
  22. kube-system   kube-apiserver-mcw7            1/1     Running            2                8h      10.0.0.137   mcw7   <none>           <none>
  23. kube-system   kube-controller-manager-mcw7   1/1     Running            4 (4h59m ago)    8h      10.0.0.137   mcw7   <none>           <none>
  24. kube-system   kube-flannel-ds-5pxmj          0/1     CrashLoopBackOff   50 (2m18s ago)   3h58m   10.0.0.138   mcw8   <none>           <none>
  25. kube-system   kube-flannel-ds-8gzfq          1/1     Running            0                5h4m    10.0.0.137   mcw7   <none>           <none>
  26. kube-system   kube-flannel-ds-s4qmj          0/1     CrashLoopBackOff   43 (2m42s ago)   3h21m   10.0.0.139   mcw9   <none>           <none>
  27. kube-system   kube-proxy-4lmsx               1/1     Running            0                3h58m   10.0.0.138   mcw8   <none>           <none>
  28. kube-system   kube-proxy-c5zmm               1/1     Running            0                8h      10.0.0.137   mcw7   <none>           <none>
  29. kube-system   kube-proxy-npmtv               1/1     Running            0                3h21m   10.0.0.139   mcw9   <none>           <none>
  30. kube-system   kube-scheduler-mcw7            1/1     Running            3 (4h59m ago)    8h      10.0.0.137   mcw7   <none>           <none>
  31. [machangwei@mcw7 ~]$

查看kubelet服务

如下：普通用户加上sudo查看状态信息，展示的信息更多。这是kubernetes中，唯一没有以容器形式运行的Kubernertes组件

  1. [machangwei@mcw7 ~]$ systemctl status kubelet.service
  2. ● kubelet.service - kubelet: The Kubernetes Node Agent
  3.    Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)
  4.   Drop-In: /usr/lib/systemd/system/kubelet.service.d
  5.            └─10-kubeadm.conf
  6.    Active: active (running) since Mon 2022-01-03 20:54:48 CST; 8h ago
  7.      Docs: https://kubernetes.io/docs/
  8.  Main PID: 41877 (kubelet)
  9.    Memory: 65.6M
  10.    CGroup: /system.slice/kubelet.service
  11.            └─41877 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.ya...
  12. [machangwei@mcw7 ~]$
  13. [machangwei@mcw7 ~]$
  14. [machangwei@mcw7 ~]$ sudo systemctl status kubelet.service
  15. ● kubelet.service - kubelet: The Kubernetes Node Agent
  16.    Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)
  17.   Drop-In: /usr/lib/systemd/system/kubelet.service.d
  18.            └─10-kubeadm.conf
  19.    Active: active (running) since Mon 2022-01-03 20:54:48 CST; 8h ago
  20.      Docs: https://kubernetes.io/docs/
  21.  Main PID: 41877 (kubelet)
  22.    Memory: 65.6M
  23.    CGroup: /system.slice/kubelet.service
  24.            └─41877 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.ya...
  25.  
  26. Jan 04 00:45:22 mcw7 kubelet[41877]: I0104 00:45:22.882382   41877 trace.go:205] Trace[1175956662]: "iptables ChainExists" (04-Jan-2022 00:45:06.975) (total time: 15906ms):
  27. Jan 04 00:45:22 mcw7 kubelet[41877]: Trace[1175956662]: [15.906635619s] [15.906635619s] END
  28. Jan 04 00:45:22 mcw7 kubelet[41877]: W0104 00:45:22.908527   41877 reflector.go:442] k8s.io/client-go/informers/factory.go:134: watch of *v1.RuntimeClass ended with: an error ...
  29. Jan 04 00:45:22 mcw7 kubelet[41877]: W0104 00:45:22.908592   41877 reflector.go:442] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:66: watch of *v1.Pod ended with: an erro...
  30. Jan 04 00:45:23 mcw7 kubelet[41877]: W0104 00:45:22.909431   41877 reflector.go:442] object-"kube-system"/"kube-flannel-cfg": watch of *v1.ConfigMap ended with: an error on th...
  31. Jan 04 00:45:23 mcw7 kubelet[41877]: W0104 00:45:22.909490   41877 reflector.go:442] object-"kube-system"/"kube-proxy": watch of *v1.ConfigMap ended with: an error...m succeeding
  32. Jan 04 00:45:23 mcw7 kubelet[41877]: E0104 00:45:22.685903   41877 event.go:276] Unable to write event: '&v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, Ob...55", Generat
  33. Jan 04 00:45:24 mcw7 kubelet[41877]: E0104 00:45:24.372904   41877 kubelet.go:2157] "Housekeeping took longer than 15s" err="housekeeping took too long" seconds=43.320536225
  34. Jan 04 00:45:33 mcw7 kubelet[41877]: I0104 00:45:33.740561   41877 scope.go:110] "RemoveContainer" containerID="742e24b700514948f23ae7b06ded37b1c9234a05ac13fdd08f80aab0889c35ad"
  35. Jan 04 00:45:33 mcw7 kubelet[41877]: I0104 00:45:33.879840   41877 scope.go:110] "RemoveContainer" containerID="de11102a90f955da94d5e316b3ada4adbfef6cc7b60cbae25c43f7396b0407a3"
  36. Hint: Some lines were ellipsized, use -l to show in full.

应用部署案例：httpd(一个问题解决：/run/flannel/subnet.env: no such file or directory)

--replicas已经被弃用了，无法kubectl run指定副本数
下面包含遇到的 一个问题：/run/flannel/subnet.env: no such file or directory

部署应用

  1. [machangwei@mcw7 ~]$ kubectl run httpd-app --image=httpd --replicas=1
  2. Error: unknown flag: --replicas
  3. See 'kubectl run --help' for usage.
  4. [machangwei@mcw7 ~]$ kubectl run httpd-app --image=httpd --env="replicas=2"  #将它放在里面，
  5. pod/httpd-app created                                          #但是副本是默认的1，这样env跟副本没关系

查看部署的应用

  1. [machangwei@mcw7 ~]$ kubectl get deployment #当前没有部署好 的应用
  2. No resources found in default namespace.
  3. [machangwei@mcw7 ~]$ kubectl get pod  #查看刚刚部署的应用情况，这里状态一直是这样的ContainerCreating，5分钟过去还是么有改变
  4. NAME        READY   STATUS              RESTARTS   AGE
  5. httpd-app   0/1     ContainerCreating   0          2m1s
  6. [machangwei@mcw7 ~]$ kubectl get pod -o wide
  7. NAME        READY   STATUS              RESTARTS   AGE    IP       NODE   NOMINATED NODE   READINESS GATES
  8. httpd-app   0/1     ContainerCreating   0          1

查看跑起来的容器有哪些，看刚刚创建的容器POD详情

  1. [machangwei@mcw7 ~]$ kubectl get pod --all-namespaces
  2. NAMESPACE     NAME                           READY   STATUS              RESTARTS         AGE
  3. default       httpd-app                      0/1     ContainerCreating   0                6m3s
  4. kube-system   coredns-6d8c4cb4d-2296m        1/1     Running             1 (5h58m ago)    9h
  5. kube-system   coredns-6d8c4cb4d-lphb2        1/1     Running             1 (5h58m ago)    9h
  6. kube-system   etcd-mcw7                      1/1     Running             3                9h
  7. kube-system   kube-apiserver-mcw7            1/1     Running             2                9h
  8. kube-system   kube-controller-manager-mcw7   1/1     Running             4 (5h58m ago)    9h
  9. kube-system   kube-flannel-ds-5pxmj          0/1     CrashLoopBackOff    61 (4m38s ago)   4h57m
  10. kube-system   kube-flannel-ds-8gzfq          1/1     Running             0                6h3m
  11. kube-system   kube-flannel-ds-s4qmj          0/1     CrashLoopBackOff    55 (30s ago)     4h20m
  12. kube-system   kube-proxy-4lmsx               1/1     Running             0                4h57m
  13. kube-system   kube-proxy-c5zmm               1/1     Running             0                9h
  14. kube-system   kube-proxy-npmtv               1/1     Running             0                4h20m
  15. kube-system   kube-scheduler-mcw7            1/1     Running             3 (5h58m ago)    9h

由上面可知，刚刚部署的应用是 httpd-app ，namespace是default。状态是ContainerCreating，没有ready。而且只有一个，不是两个副本
根据上面的信息查看部署详情。貌似我看到 Environment: replicas: 2，这里应该是当成系统环境变量了

  1. [machangwei@mcw7 ~]$  kubectl describe pod httpd-app --namespace=default
  2. Name:         httpd-app
  3. Namespace:    default
  4. Priority:     0
  5. Node:         mcw9/10.0.0.139
  6. Start Time:   Tue, 04 Jan 2022 06:38:04 +0800
  7. Labels:       run=httpd-app
  8. Annotations:  <none>
  9. Status:       Pending
  10. IP:
  11. IPs:          <none>
  12. Containers:
  13.   httpd-app:
  14.     Container ID:
  15.     Image:          httpd
  16.     Image ID:
  17.     Port:           <none>
  18.     Host Port:      <none>
  19.     State:          Waiting
  20.       Reason:       ContainerCreating
  21.     Ready:          False
  22.     Restart Count:  0
  23.     Environment:
  24.       replicas:  2
  25.     Mounts:
  26.       /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-728h9 (ro)
  27. Conditions:
  28.   Type              Status
  29.   Initialized       True
  30.   Ready             False
  31.   ContainersReady   False
  32.   PodScheduled      True
  33. Volumes:
  34.   kube-api-access-728h9:
  35.     Type:                    Projected (a volume that contains injected data from multiple sources)
  36.     TokenExpirationSeconds:  3607
  37.     ConfigMapName:           kube-root-ca.crt
  38.     ConfigMapOptional:       <nil>
  39.     DownwardAPI:             true
  40. QoS Class:                   BestEffort
  41. Node-Selectors:              <none>
  42. Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
  43.                              node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
  44. Events:
  45.   Type     Reason                  Age                     From               Message
  46.   ----     ------                  ----                    ----               -------
  47.   Normal   Scheduled               7m3s                    default-scheduler  Successfully assigned default/httpd-app to mcw9
  48.   Warning  FailedCreatePodSandBox  6m56s                   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "80e204314b98b32c3ec47b12288e6888ef3a6cd4923a6e7ee9e77a072ef1189d" network for pod "httpd-app": networkPlugin cni failed to set up pod "httpd-app_default" network: open /run/flannel/subnet.env: no such file or directory
  49.   Warning  FailedCreatePodSandBox  6m54s                   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "1db6657c883c79ff176ce5523f4e6e7dbd3a65278cf20777cf7e870f7b17473f" network for pod "httpd-app": networkPlugin cni failed to set up pod "httpd-app_default" network: open /run/flannel/subnet.env: no such file or directory
  50.   Warning  FailedCreatePodSandBox  6m47s                   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "e2dc2971e915be8a693190d244bbd2b4c31a86ecc5ed7f11d48b89f913121cd2" network for pod "httpd-app": networkPlugin cni failed to set up pod "httpd-app_default" network: open /run/flannel/subnet.env: no such file or directory
  51.   Warning  FailedCreatePodSandBox  6m34s                   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "c8a67cd41221a857c1795bf9739ecc68970fca82a06680b5093e915a48762b9c" network for pod "httpd-app": networkPlugin cni failed to set up pod "httpd-app_default" network: open /run/flannel/subnet.env: no such file or directory
  52.   Warning  FailedCreatePodSandBox  6m33s                   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "574f061c8b01b9ac54a72d81dee6d8844cf375d7862335590a2a38ed66fcefa1" network for pod "httpd-app": networkPlugin cni failed to set up pod "httpd-app_default" network: open /run/flannel/subnet.env: no such file or directory
  53.   Warning  FailedCreatePodSandBox  6m32s                   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "87f12760cfe8079bd3fc709327bd99f93b1cf2284b9832f748937a98db25a6d5" network for pod "httpd-app": networkPlugin cni failed to set up pod "httpd-app_default" network: open /run/flannel/subnet.env: no such file or directory
  54.   Warning  FailedCreatePodSandBox  6m31s                   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "eb12e226a4233698e8aef1618910cfaad49be474363be9243fd2f9eced60f754" network for pod "httpd-app": networkPlugin cni failed to set up pod "httpd-app_default" network: open /run/flannel/subnet.env: no such file or directory
  55.   Warning  FailedCreatePodSandBox  6m30s                   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "19c042430da85875f567bb9a872a559c423fc25acef91ffa154795e3bd8bbd75" network for pod "httpd-app": networkPlugin cni failed to set up pod "httpd-app_default" network: open /run/flannel/subnet.env: no such file or directory
  56.   Warning  FailedCreatePodSandBox  6m29s                   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "670f4e24adcbe325b2b77a01a7a4e05d483ceb95dbcadf97bdf26dff1afd171d" network for pod "httpd-app": networkPlugin cni failed to set up pod "httpd-app_default" network: open /run/flannel/subnet.env: no such file or directory
  57.   Normal   SandboxChanged          6m25s (x12 over 6m55s)  kubelet            Pod sandbox changed, it will be killed and re-created.
  58.   Warning  FailedCreatePodSandBox  116s (x251 over 6m28s)  kubelet            (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "59edf6c07ceb9dc2db9eb5ba0a0b7263de5a2ab70099ba48c09a6867ef2e8084" network for pod "httpd-app": networkPlugin cni failed to set up pod "httpd-app_default" network: open /run/flannel/subnet.env: no such file or directory
  59. [machangwei@mcw7 ~]$

journalctl  -u kubelet

journalctl  -u kubelet 这个命令普通用户不能用，root在各个节点都能用，但是不太方便找错误信息，我只会一点点往下拖进度

  1. [root@mcw8 ~]$ journalctl  -u kubelet
  2. -- Logs begin at Mon 2022-01-03 17:32:08 CST, end at Tue 2022-01-04 06:58:19 CST. --
  3. Jan 03 18:10:12 mcw8 systemd[1]: Started kubelet: The Kubernetes Node Agent.
  4. Jan 03 18:10:12 mcw8 systemd[1]: Starting kubelet: The Kubernetes Node Agent...
  5. Jan 03 18:10:13 mcw8 kubelet[1940]: E0103 18:10:13.589113    1940 server.go:205] "Failed to load kubelet config file" err="failed to load Kubelet config file /var/lib/kubelet/con
  6. Jan 03 18:10:13 mcw8 systemd[1]: kubelet.service: main process exited, code=exited, status=1/FAILURE
  7. Jan 03 18:10:13 mcw8 systemd[1]: Unit kubelet.service entered failed state.

上面看到错误信息是：Failed to create pod sandbox: ...open /run/flannel/subnet.env: no such file or directory
然后我用root看了下，这个文件是存在的，
因为我是普通用户执行部署应用的，部署报错没有这个文件，会不会是我没有它的写权限呢？我是修改这个文件设置其它人可以写或者是
用root去部署应用就可以了吗？试一下
[root@mcw7 ~]$ ls /run/flannel/subnet.env -l
-rw-r--r-- 1 root root 96 Jan 4 00:42 /run/flannel/subnet.env

试试root部署应用

  1. [root@mcw7 ~]$ kubectl run mcw1httpd-app --image=httpd  #我用root部署应用，但是报错了
  2. The connection to the server localhost:8080 was refused - did you specify the right host or port?
  3. [machangwei@mcw7 ~]$ kubectl run mcw1httpd-app --image=httpd #用普通用户就可以。果然root部署应用，好像哪里有点问题
  4. pod/mcw1httpd-app created
  5. [machangwei@mcw7 ~]$ kubectl get pod
  6. NAME            READY   STATUS              RESTARTS   AGE
  7. httpd-app       0/1     ContainerCreating   0          31m
  8. mcw1httpd-app   0/1     ContainerCreating   0          66s
  1. [machangwei@mcw7 ~]$ kubectl get pod --all-namespaces
  2. [machangwei@mcw7 ~]$  kubectl describe pod httpd-app --namespace=default #根据命令查出容器创建所在的节点，
  3. Name:         httpd-app
  4. Namespace:    default
  5. Priority:     0
  6. Node:         mcw9/10.0.0.139  #是mcw9节点。

于是从mcw9节点上去查看，发现有httpd-app容器不断的在销毁和重新创建。跟据kubectl describe pod httpd-app --namespace=default查出的后面的详情，那也是有很多个记录，应该是重试记录。

  1. [root@mcw9 ~]$ docker ps
  2. CONTAINER ID   IMAGE                                                COMMAND                  CREATED       STATUS       PORTS     NAMES
  3. 881e2618fa9d   registry.aliyuncs.com/google_containers/kube-proxy   "/usr/local/bin/kube…"   5 hours ago   Up 5 hours             k8s_kube-proxy_kube-proxy-npmtv_kube-system_7f6b0d03-0d35-48ae-b091-5f1e0618ba85_0
  4. 75e85cb833df   registry.aliyuncs.com/google_containers/pause:3.6    "/pause"                 5 hours ago   Up 5 hours             k8s_POD_kube-proxy-npmtv_kube-system_7f6b0d03-0d35-48ae-b091-5f1e0618ba85_0
  5. 625efe596472   registry.aliyuncs.com/google_containers/pause:3.6    "/pause"                 5 hours ago   Up 5 hours             k8s_POD_kube-flannel-ds-s4qmj_kube-system_a8082592-8c92-4c48-98dc-c6b52ebb9498_0
  6. [root@mcw9 ~]$ docker ps
  7. CONTAINER ID   IMAGE                                                COMMAND                  CREATED        STATUS                  PORTS     NAMES
  8. d7f65cd3d025   registry.aliyuncs.com/google_containers/pause:3.6    "/pause"                 1 second ago   Up Less than a second             k8s_POD_httpd-app_default_bb6090a2-b5e4-48a3-99b5-082bcc8f8d13_1934

主节点上看kubectl describe pod httpd-app

--namespace=default报错信息，是没有/run/flannel/subnet.env文件。n，但是在node节点是不存在这个文件的。；这个文件是属于flannel网络的。那么，是否是主节点让node节点创建容器，node节点没有要在node本地找这个文件吗？如果是，那么岂不是node本地也应该创建flannel网络呢？刚刚看了下资料。貌似架构图中是，每个节点都需要部署flannel服务的

Warning FailedCreatePodSandBox 116s (x251 over 6m28s) kubelet (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "59edf6c07ceb9dc2db9eb5ba0a0b7263de5a2ab70099ba48c09a6867ef2e8084" network for pod "httpd-app": networkPlugin cni failed to set up pod "httpd-app_default" network: open /run/flannel/subnet.env: no such file or directory

可是我再node节点上 看了下，是部署了这个flannel网络的。那么为什么node节点没有/run/flannel/subnet.env这个文件呢，无法部署好应用是否和它有关系呢？

  1. [root@mcw8 ~]$ docker ps |awk '{print $NF}'
  2. NAMES
  3. k8s_kube-proxy_kube-proxy-4lmsx_kube-system_fb743f5c-0f44-43a7-ad7e-78817ddafc12_0
  4. k8s_POD_kube-flannel-ds-5pxmj_kube-system_0972d5b3-a774-44cc-94b1-6765ec8f4256_0
  5. k8s_POD_kube-proxy-4lmsx_kube-system_fb743f5c-0f44-43a7-ad7e-78817ddafc12_0
  6. [root@mcw8 ~]$

网上解决方案：open /run/flannel/subnet.env: no such file or directory

查看pod的信息时发现报错：open /run/flannel/subnet.env: no such file or directory

一是查看各个节点，包括master 节点是否有/run/flannel/subnet.env，内容应该是类似如下：

FLANNEL_NETWORK=10.244.0.0/16
FLANNEL_SUBNET=10.244.0.1/24
FLANNEL_MTU=1450
FLANNEL_IPMASQ=true
若有节点没有该文件那就拷贝一份。

二是在kubeadm init时是否添加标签--pod-network-cidr=10.244.0.0/16这样式的。如果环境允许可以 kubeadm reset，再重新init。

查看node节点，有目录但是没有文件

  1. root@mcw8 ~]$ ls /run/flannel/
  2. [root@mcw8 ~]$ 
  3.  
  4. [root@mcw9 ~]$ ls /run/flannel/
  5. [root@mcw9 ~]$

在master节点，将这个文件复制过去

  1. [root@mcw7 ~]$ ls /run/flannel/subnet.env
  2. /run/flannel/subnet.env
  3. [root@mcw7 ~]$ scp /run/flannel/subnet.env 10.0.0.138:/run/flannel/
  4. root@10.0.0.138's password:
  5. subnet.env                                                                                                                                      100%   96   230.1KB/s   00:00
  6. [root@mcw7 ~]$ scp /run/flannel/subnet.env 10.0.0.139:/run/flannel/
  7. root@10.0.0.139's password:
  8. subnet.env                                                                                                                                      100%   96    88.6KB/s   00:00
  9. [root@mcw7 ~]$

然后在master节点用普通用户获取pod，发现有一个部署的应用已经是ready了，状态已经是running了

  1. [machangwei@mcw7 ~]$ kubectl get pod
  2. NAME            READY   STATUS              RESTARTS   AGE
  3. httpd-app       1/1     Running             0          63m
  4. mcw1httpd-app   0/1     ContainerCreating   0          33m

打完上面的字再查看，部署的两个应用都好了

  1. [machangwei@mcw7 ~]$ kubectl get pod
  2. NAME            READY   STATUS    RESTARTS   AGE
  3. httpd-app       1/1     Running   0          64m
  4. mcw1httpd-app   1/1     Running   0          34m

部署的应用 POD 状态是running后信息查看

  1. [machangwei@mcw7 ~]$ kubectl get pod  #获取pod信息，刚刚部署的两个应用，状态running
  2. NAME            READY   STATUS    RESTARTS   AGE
  3. httpd-app       1/1     Running   0          67m
  4. mcw1httpd-app   1/1     Running   0          37m
  5. [machangwei@mcw7 ~]$ kubectl get pod -o wide  #加上参数，可以看到ip和node节点，ip是一样的，不知道咋回事
  6. NAME            READY   STATUS    RESTARTS   AGE   IP           NODE   NOMINATED NODE   READINESS GATES
  7. httpd-app       1/1     Running   0          67m   10.244.0.2   mcw9   <none>           <none>
  8. mcw1httpd-app   1/1     Running   0          37m   10.244.0.2   mcw8   <none>           <none>
  9. [machangwei@mcw7 ~]$ kubectl get deployment
  10. No resources found in default namespace.
  11. [machangwei@mcw7 ~]$ kubectl get pod --all-namespaces #如下可以看到刚刚部署的两个应用，都是属于default的namespace
  12. NAMESPACE     NAME                           READY   STATUS             RESTARTS         AGE
  13. default       httpd-app                      1/1     Running            0                69m
  14. default       mcw1httpd-app                  1/1     Running            0                39m
  15. kube-system   coredns-6d8c4cb4d-2296m        1/1     Running            1 (7h2m ago)     10h
  16. kube-system   coredns-6d8c4cb4d-lphb2        1/1     Running            1 (7h1m ago)     10h
  17. kube-system   etcd-mcw7                      1/1     Running            3                10h
  18. kube-system   kube-apiserver-mcw7            1/1     Running            2                10h
  19. kube-system   kube-controller-manager-mcw7   1/1     Running            4 (7h2m ago)     10h
  20. kube-system   kube-flannel-ds-5pxmj          0/1     CrashLoopBackOff   74 (93s ago)     6h1m
  21. kube-system   kube-flannel-ds-8gzfq          1/1     Running            0                7h7m
  22. kube-system   kube-flannel-ds-s4qmj          0/1     CrashLoopBackOff   67 (2m17s ago)   5h23m
  23. kube-system   kube-proxy-4lmsx               1/1     Running            0                6h1m
  24. kube-system   kube-proxy-c5zmm               1/1     Running            0                10h
  25. kube-system   kube-proxy-npmtv               1/1     Running            0                5h23m
  26. kube-system   kube-scheduler-mcw7            1/1     Running            3 (7h2m ago)     10h
  27.  
  28. [machangwei@mcw7 ~]$ kubectl get pod --all-namespaces -o wide #加上参数查看
  29. NAMESPACE     NAME                           READY   STATUS             RESTARTS         AGE     IP           NODE   NOMINATED NODE   READINESS GATES
  30. default       httpd-app                      1/1     Running            0                73m     10.244.0.2   mcw9   <none>           <none>
  31. default       mcw1httpd-app                  1/1     Running            0                43m     10.244.0.2   mcw8   <none>           <none>

kubernetes部署第一个应用案例的更多相关文章

  1. kubernetes部署一个应用程序

    文章原文 部署 nginx Deployment 如果你已经完成了Kubernetes的搭建,那我跟我一块来部署第一个应用程序吧.没有完成 Kubernetes 集群搭建的,请参考文档 使用 kube ...

  2. ENode 2.0 - 第一个真实案例剖析-一个简易论坛（Forum）

    前言 经过不断的坚持和努力,ENode 2.0的第一个真实案例终于出来了.这个案例是一个简易的论坛,开发这个论坛的初衷是为了验证用ENode框架来开发一个真实项目的可行性.目前这个论坛在UI上是使用了 ...

  3. K8S学习笔记之Kubernetes 部署策略详解

    0x00 概述 在Kubernetes中有几种不同的方式发布应用,所以为了让应用在升级期间依然平稳提供服务,选择一个正确的发布策略就非常重要了. 选择正确的部署策略是要依赖于我们的业务需求的,下面我们 ...

  4. Kubernetes 部署失败的 10 个最普遍原因

    [原文].后面我们可能还会看到一个 OOMKilled 错误. 我们的应用正在挂掉?为什么? 首先我们查看应用日志.假定你发送应用日志到 stdout(事实上你也应该这么做),你可以使用 kubect ...

  5. Kubernetes部署通用手册 (支持版本1.19,1.18,1.17,1.16)

    Kubernetes平台环境规划 操作环境 rbac 划分(HA高可用双master部署实例) 本文穿插了ha 高可用部署的实例,当前章节设计的是ha部署双master 部署 内网ip 角色 安装软件 ...

  6. Kubernetes 部署策略详解-转载学习

    Kubernetes 部署策略详解 参考:https://www.qikqiak.com/post/k8s-deployment-strategies/ 在Kubernetes中有几种不同的方式发布应 ...

  7. [系统集成] 基于Kubernetes 部署 jenkins 并动态分配资源

    基于kubernetes 部署 jenkins master 比较简单,难点是为 jenkins 动态分配资源.基于kubernetes 为 jenkins 动态分配资源需要实现下述功能: 资源分配: ...

  8. kubernetes 部署

    kubernetes 部署(Centos 7) 一个或者多个兼容 deb 或者 rpm 软件包的操作系统,比如 Ubuntu 或者 CentOS 每台机器 2 GB 以上的内存,内存不足时应用会受限制 ...

  9. nuclio kubernetes 部署

    一张参考架构图: 从图中可以看到nuclio可以运行到docker 以及kubernetes中 提供了kubernetes 部署的脚本 安装 创建命名空间 kubectl create namespa ...

随机推荐

  1. 100个Shell脚本——【脚本4】自定义rm命令

    [脚本4]自定义rm命令 linux系统的rm命令太危险,一不小心就会删除掉系统文件. 写一个shell脚本来替换系统的rm命令,要求当删除一个文件或者目录时,都要做一个备份,然后再删除.下面分两种情 ...

  2. OpenStack之十： 安装dashboard

    官网地址 https://docs.openstack.org/horizon/stein/install/install-rdo.html #:安装包 [root@cobbler ~]# yum i ...

  3. 【Java 多线程】Java线程池类ThreadPoolExecutor、ScheduledThreadPoolExecutor及Executors工厂类

    Java中的线程池类有两个,分别是:ThreadPoolExecutor和ScheduledThreadPoolExecutor,这两个类都继承自ExecutorService.利用这两个类,可以创建 ...

  4. Java分层思想

    从最常规的分层结构来说,系统层次从上到下依次为: 表现层/UI层/界面层:主要是客户端的展示. 服务层/业务层:直接为客户端提供的服务或功能.也是系统所能对外提供的功能. 领域层:系统内的领域活动. ...

  5. Pythonweb采集

    一.访问页面 import webbrowser webbrowser.open('http://www.baidu.com/')    pip3 install requests import re ...

  6. Redis增加测试数据

    目录 一.简介 二.操作 三.制造测试数据 一.简介 用shell脚本将文本内容挨个写到redis中效率是很慢的.打开一个链接,写入后再关闭,再打开,效率很低. redis支持pipe mode功能, ...

  7. Nginx支持php

    目录 一.简介 二.配置 三.测试 四.参数 一.简介 Nginx本身只能解析html文件,但有些网页是php写的,就需要Nginx连接php,将网页解析成html再发给客户端. 配置中将.php 结 ...

  8. JS 中常用的去重

    第一种:indexOf (获取字符串值在字符串中首次出现的位置,若没有这个值,则返回-1) let arr = [15,45,88,45,78,15,55,88]; let arr1 = []; // ...

  9. OpenGL ES2 缩放移动

    OpenGL ES Transformations with Gestures Ricardo Rendon Cepeda on December 10, 2013 Tweet Gestures: I ...

  10. 【论文笔记】 Denoising Implicit Feedback for Recommendation

    Denoising Implicit Feedback for Recommendation Authors: 王文杰,冯福利,何向南,聂礼强,蔡达成 WSDM'21 新加坡国立大学,中国科学技术大学 ...