run 或create deployment 部署一个应用

kubernetes 部署 nginx ，使用 kubectl get deployment 时出现 No resources found in default namespace

结果验证：
kubectl run mcw01_nginx --image=nginx #能get pod，但不能get deployment ，不能get replicaset
kubectl create deployment mcw01dep-nginx --image=nginx #既能get pod ，又能get deployment，又能get replicaset

kubectl run nginx-deployment --image=nginx:1.7.9 --replicas=2 #它不能 创建副本了，
kubectl create deployment mcw01dep-nginx --image=nginx #那么这个命令是否可以支持创建多个副本

首先我确保了master和nodes节点的正常运行，还有各个组件处于健康状态
使用 kubectl 命令创建监听 80 端口的 Nginx Pod（Kubernetes 运行容器的最小单元）
kubectl run mcw01_nginx --image=nginx --port=80
运行结果:

  1. [machangwei@mcw7 ~]$ kubectl run nginx-deployment --image=nginx:1.7.9 --replicas=2
  2. Error: unknown flag: --replicas
  3. See 'kubectl run --help' for usage.
  4. [machangwei@mcw7 ~]$ kubectl run mcw01_nginx --image=nginx --port=80  #不能使用下划线命名，但是可以用短横线
  5. The Pod "mcw01_nginx" is invalid:
  6. * metadata.name: Invalid value: "mcw01_nginx": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
  7. * spec.containers[0].name: Invalid value: "mcw01_nginx": a lowercase RFC 1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name',  or '123-abc', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?')
  8. [machangwei@mcw7 ~]$
  9. [machangwei@mcw7 ~]$ kubectl run mcw01-nginx --image=nginx --port=80
  10. pod/mcw01-nginx created

可以看到，这里提示只是成功创建了一个pod 叫mcw01_nginx，在以往的版本中似乎会顺便创建一个deployment，显然这里没有

使用 kubectl get deployment命令查看deployment

  1. [machangwei@mcw7 ~]$ kubectl get deployment
  2. No resources found in default namespace.

问题就出现了，的确没有，那我们就需要手动创建

使用 kubectl create deployment mcw01dep-nginx --image=nginx

  1. [machangwei@mcw7 ~]$ kubectl create deployment mcw01dep-nginx --image=nginx
  2. deployment.apps/mcw01dep-nginx created

再次使用kubectl get deployment查看,可以看到已经有了一个mcw01dep-nginx 的 deployment

  1. [machangwei@mcw7 ~]$ kubectl get deployment
  2. NAME             READY   UP-TO-DATE   AVAILABLE   AGE
  3. mcw01dep-nginx   1/1     1            1           48s

再次使用kubectl get replicaset看副本，有mcw01dep-nginx命名的副本

  1. [machangwei@mcw7 ~]$ kubectl get replicaset
  2. NAME                        DESIRED   CURRENT   READY   AGE
  3. mcw01dep-nginx-5dd785954d   1         1         1       6m26s

使用kubectl get pod也能看到mcw01dep-nginx命名的Pod。

  1. [machangwei@mcw7 ~]$ kubectl get pod
  2. NAME                              READY   STATUS    RESTARTS   AGE
  3. httpd-app                         1/1     Running   0          3h12m
  4. mcw01-nginx                       1/1     Running   0          3m55s
  5. mcw01dep-nginx-5dd785954d-sb8ps   1/1     Running   0          94s
  6. mcw1httpd-app                     1/1     Running   0          162m
  7. nginx-deployment                  1/1     Running   0          12m

查看刚刚部署的应用

  1. [machangwei@mcw7 ~]$ kubectl get deployment
  2. NAME             READY   UP-TO-DATE   AVAILABLE   AGE
  3. mcw01dep-nginx   1/1     1            1           9m37s
  4. [machangwei@mcw7 ~]$ kubectl describe deployment mcw01dep-nginx
  5. Name:                   mcw01dep-nginx
  6. Namespace:              default
  7. CreationTimestamp:      Tue, 04 Jan 2022 09:49:28 +0800
  8. Labels:                 app=mcw01dep-nginx
  9. Annotations:            deployment.kubernetes.io/revision: 1
  10. Selector:               app=mcw01dep-nginx
  11. Replicas:               1 desired | 1 updated | 1 total | 1 available | 0 unavailable
  12. StrategyType:           RollingUpdate
  13. MinReadySeconds:        0
  14. RollingUpdateStrategy:  25% max unavailable, 25% max surge
  15. Pod Template:
  16.   Labels:  app=mcw01dep-nginx
  17.   Containers:
  18.    nginx:
  19.     Image:        nginx
  20.     Port:         <none>
  21.     Host Port:    <none>
  22.     Environment:  <none>
  23.     Mounts:       <none>
  24.   Volumes:        <none>
  25. Conditions:
  26.   Type           Status  Reason
  27.   ----           ------  ------
  28.   Available      True    MinimumReplicasAvailable
  29.   Progressing    True    NewReplicaSetAvailable
  30. OldReplicaSets:  <none>
  31. NewReplicaSet:   mcw01dep-nginx-5dd785954d (1/1 replicas created)
  32. Events:
  33.   Type    Reason             Age   From                   Message
  34.   ----    ------             ----  ----                   -------
  35.   Normal  ScalingReplicaSet  10m   deployment-controller  Scaled up replica set mcw01dep-nginx-5dd785954d to 1

查看刚刚部署的应用的副本

  1. [machangwei@mcw7 ~]$ kubectl get replicaset
  2. NAME                        DESIRED   CURRENT   READY   AGE
  3. mcw01dep-nginx-5dd785954d   1         1         1       15m
  4. [machangwei@mcw7 ~]$ kubectl describe replicaset mcw01dep-nginx-5dd785954d
  5. Name:           mcw01dep-nginx-5dd785954d
  6. Namespace:      default
  7. Selector:       app=mcw01dep-nginx,pod-template-hash=5dd785954d
  8. Labels:         app=mcw01dep-nginx
  9.                 pod-template-hash=5dd785954d
  10. Annotations:    deployment.kubernetes.io/desired-replicas: 1
  11.                 deployment.kubernetes.io/max-replicas: 2
  12.                 deployment.kubernetes.io/revision: 1
  13. Controlled By:  Deployment/mcw01dep-nginx
  14. Replicas:       1 current / 1 desired
  15. Pods Status:    1 Running / 0 Waiting / 0 Succeeded / 0 Failed
  16. Pod Template:
  17.   Labels:  app=mcw01dep-nginx
  18.            pod-template-hash=5dd785954d
  19.   Containers:
  20.    nginx:
  21.     Image:        nginx
  22.     Port:         <none>
  23.     Host Port:    <none>
  24.     Environment:  <none>
  25.     Mounts:       <none>
  26.   Volumes:        <none>
  27. Events:
  28.   Type    Reason            Age   From                   Message
  29.   ----    ------            ----  ----                   -------
  30.   Normal  SuccessfulCreate  15m   replicaset-controller  Created pod: mcw01dep-nginx-5dd785954d-sb8ps

查看刚刚部署的应用的Pod信息

  1. [machangwei@mcw7 ~]$ kubectl describe pod mcw01dep-nginx-5dd785954d-sb8ps
  2. Name:         mcw01dep-nginx-5dd785954d-sb8ps
  3. Namespace:    default
  4. Priority:     0
  5. Node:         mcw9/10.0.0.139
  6. Start Time:   Tue, 04 Jan 2022 09:49:27 +0800
  7. Labels:       app=mcw01dep-nginx
  8.               pod-template-hash=5dd785954d
  9. Annotations:  <none>
  10. Status:       Running
  11. IP:           10.244.0.4
  12. IPs:
  13.   IP:           10.244.0.4
  14. Controlled By:  ReplicaSet/mcw01dep-nginx-5dd785954d
  15. Containers:
  16.   nginx:
  17.     Container ID:   docker://374ff9c1a60e9562f7e05ec4eaa5150e3380b836a26f3b0fe565e6f9dea52cef
  18.     Image:          nginx
  19.     Image ID:       docker-pullable://nginx@sha256:0d17b565c37bcbd895e9d92315a05c1c3c9a29f762b011a10c54a66cd53c9b31
  20.     Port:           <none>
  21.     Host Port:      <none>
  22.     State:          Running
  23.       Started:      Tue, 04 Jan 2022 09:49:30 +0800
  24.     Ready:          True
  25.     Restart Count:  0
  26.     Environment:    <none>
  27.     Mounts:
  28.       /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-h56zh (ro)
  29. Conditions:
  30.   Type              Status
  31.   Initialized       True
  32.   Ready             True
  33.   ContainersReady   True
  34.   PodScheduled      True
  35. Volumes:
  36.   kube-api-access-h56zh:
  37.     Type:                    Projected (a volume that contains injected data from multiple sources)
  38.     TokenExpirationSeconds:  3607
  39.     ConfigMapName:           kube-root-ca.crt
  40.     ConfigMapOptional:       <nil>
  41.     DownwardAPI:             true
  42. QoS Class:                   BestEffort
  43. Node-Selectors:              <none>
  44. Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
  45.                              node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
  46. Events:
  47.   Type    Reason     Age   From               Message
  48.   ----    ------     ----  ----               -------
  49.   Normal  Scheduled  18m   default-scheduler  Successfully assigned default/mcw01dep-nginx-5dd785954d-sb8ps to mcw9
  50.   Normal  Pulling    18m   kubelet            Pulling image "nginx"
  51.   Normal  Pulled     18m   kubelet            Successfully pulled image "nginx" in 1.193138975s
  52.   Normal  Created    18m   kubelet            Created container nginx
  53.   Normal  Started    18m   kubelet            Started container nginx

指定命名空间的查询Pod详情，应该是一样的

  1. [machangwei@mcw7 ~]$ kubectl get pod --all-namespaces
  2. NAMESPACE     NAME                              READY   STATUS             RESTARTS          AGE
  3. default       httpd-app                         1/1     Running            0                 3h31m
  4. default       mcw01-nginx                       1/1     Running            0                 22m
  5. default       mcw01dep-nginx-5dd785954d-sb8ps   1/1     Running            0                 20m
  6. default       mcw1httpd-app                     1/1     Running            0                 3h1m
  7. default       nginx-deployment                  1/1     Running            0                 31m
  8. kube-system   coredns-6d8c4cb4d-2296m           1/1     Running            1 (9h ago)        13h
  9. kube-system   coredns-6d8c4cb4d-lphb2           1/1     Running            1 (9h ago)        13h
  10. kube-system   etcd-mcw7                         1/1     Running            3                 13h
  11. kube-system   kube-apiserver-mcw7               1/1     Running            2                 13h
  12. kube-system   kube-controller-manager-mcw7      1/1     Running            4 (9h ago)        13h
  13. kube-system   kube-flannel-ds-5pxmj             0/1     Error              102 (5m12s ago)   8h
  14. kube-system   kube-flannel-ds-8gzfq             1/1     Running            0                 9h
  15. kube-system   kube-flannel-ds-s4qmj             0/1     CrashLoopBackOff   95 (62s ago)      7h46m
  16. kube-system   kube-proxy-4lmsx                  1/1     Running            0                 8h
  17. kube-system   kube-proxy-c5zmm                  1/1     Running            0                 13h
  18. kube-system   kube-proxy-npmtv                  1/1     Running            0                 7h46m
  19. kube-system   kube-scheduler-mcw7               1/1     Running            3 (9h ago)        13h
  20. [machangwei@mcw7 ~]$ kubectl describe pod mcw01dep-nginx-5dd785954d-sb8ps --namespace=default
  21. Name:         mcw01dep-nginx-5dd785954d-sb8ps
  22. Namespace:    default
  23. Priority:     0
  24. Node:         mcw9/10.0.0.139
  25. Start Time:   Tue, 04 Jan 2022 09:49:27 +0800
  26. Labels:       app=mcw01dep-nginx
  27.               pod-template-hash=5dd785954d
  28. Annotations:  <none>
  29. Status:       Running
  30. IP:           10.244.0.4
  31. IPs:
  32.   IP:           10.244.0.4
  33. Controlled By:  ReplicaSet/mcw01dep-nginx-5dd785954d
  34. Containers:
  35.   nginx:
  36.     Container ID:   docker://374ff9c1a60e9562f7e05ec4eaa5150e3380b836a26f3b0fe565e6f9dea52cef
  37.     Image:          nginx
  38.     Image ID:       docker-pullable://nginx@sha256:0d17b565c37bcbd895e9d92315a05c1c3c9a29f762b011a10c54a66cd53c9b31
  39.     Port:           <none>
  40.     Host Port:      <none>
  41.     State:          Running
  42.       Started:      Tue, 04 Jan 2022 09:49:30 +0800
  43.     Ready:          True
  44.     Restart Count:  0
  45.     Environment:    <none>
  46.     Mounts:
  47.       /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-h56zh (ro)
  48. Conditions:
  49.   Type              Status
  50.   Initialized       True
  51.   Ready             True
  52.   ContainersReady   True
  53.   PodScheduled      True
  54. Volumes:
  55.   kube-api-access-h56zh:
  56.     Type:                    Projected (a volume that contains injected data from multiple sources)
  57.     TokenExpirationSeconds:  3607
  58.     ConfigMapName:           kube-root-ca.crt
  59.     ConfigMapOptional:       <nil>
  60.     DownwardAPI:             true
  61. QoS Class:                   BestEffort
  62. Node-Selectors:              <none>
  63. Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
  64.                              node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
  65. Events:
  66.   Type    Reason     Age   From               Message
  67.   ----    ------     ----  ----               -------
  68.   Normal  Scheduled  21m   default-scheduler  Successfully assigned default/mcw01dep-nginx-5dd785954d-sb8ps to mcw9
  69.   Normal  Pulling    21m   kubelet            Pulling image "nginx"
  70.   Normal  Pulled     21m   kubelet            Successfully pulled image "nginx" in 1.193138975s
  71.   Normal  Created    21m   kubelet            Created container nginx
  72.   Normal  Started    21m   kubelet            Started container nginx
  73. [machangwei@mcw7 ~]$

对刚刚部署的应用做几种资源的查询

  1. [machangwei@mcw7 ~]$ kubectl get deployment
  2. NAME             READY   UP-TO-DATE   AVAILABLE   AGE
  3. mcw01dep-nginx   1/1     1            1           23m
  4. [machangwei@mcw7 ~]$ kubectl get replicaset
  5. NAME                        DESIRED   CURRENT   READY   AGE
  6. mcw01dep-nginx-5dd785954d   1         1         1       23m
  7. [machangwei@mcw7 ~]$ kubectl get pod |grep mcw01dep-nginx
  8. mcw01dep-nginx-5dd785954d-sb8ps   1/1     Running   0          23m
  9. [machangwei@mcw7 ~]$ kubectl get pod -o wide |grep mcw01dep-nginx
  10. mcw01dep-nginx-5dd785954d-sb8ps   1/1     Running   0          23m     10.244.0.4   mcw9   <none>           <none>
  11. [machangwei@mcw7 ~]$ kubectl get pod --all-namespaces |grep mcw01dep-nginx
  12. default       mcw01dep-nginx-5dd785954d-sb8ps   1/1     Running            0                 24m

创建同名的deployment是不可以的

  1. [machangwei@mcw7 ~]$ kubectl get deployment
  2. NAME             READY   UP-TO-DATE   AVAILABLE   AGE
  3. mcw01dep-nginx   1/1     1            1           31m
  4. [machangwei@mcw7 ~]$ kubectl create deployment mcw01dep-nginx --image=nginx
  5. error: failed to create deployment: deployments.apps "mcw01dep-nginx" already exists

使用负载均衡模式发布服务，让外网访问我的Nginx服务(docker)

kubectl expose deployment mcw01dep-nginx --port=80 --type=LoadBalancer

  1. [machangwei@mcw7 ~]$ kubectl get deployment
  2. NAME             READY   UP-TO-DATE   AVAILABLE   AGE
  3. mcw01dep-nginx   1/1     1            1           33m
  4. [machangwei@mcw7 ~]$ kubectl expose deployment mcw01dep-nginx --port=80 --type=LoadBalancer
  5. service/mcw01dep-nginx exposed

查看服务详情

kubectl describe service mcw01dep-nginx
输出如下：

  1. [machangwei@mcw7 ~]$ kubectl get service  #获取服务信息
  2. NAME             TYPE           CLUSTER-IP     EXTERNAL-IP   PORT(S)        AGE
  3. kubernetes       ClusterIP      10.96.0.1      <none>        443/TCP        13h
  4. mcw01dep-nginx   LoadBalancer   10.96.184.54   <pending>     80:30102/TCP   74s
  5. [machangwei@mcw7 ~]$ kubectl describe service mcw01dep-nginx
  6. Name:                     mcw01dep-nginx
  7. Namespace:                default
  8. Labels:                   app=mcw01dep-nginx
  9. Annotations:              <none>
  10. Selector:                 app=mcw01dep-nginx
  11. Type:                     LoadBalancer
  12. IP Family Policy:         SingleStack
  13. IP Families:              IPv4
  14. IP:                       10.96.184.54
  15. IPs:                      10.96.184.54
  16. Port:                     <unset>  80/TCP
  17. TargetPort:               80/TCP
  18. NodePort:                 <unset>  30102/TCP
  19. Endpoints:                10.244.0.4:80
  20. Session Affinity:         None
  21. External Traffic Policy:  Cluster
  22. Events:                   <none>

这里我就可以利用 节点的ip+暴露出来的端口 检测服务是否访问成功

  1. [machangwei@mcw7 ~]$ kubectl get pod -o wide |grep mcw01dep-nginx
  2. mcw01dep-nginx-5dd785954d-sb8ps   1/1     Running   0          43m     10.244.0.4   mcw9   <none>           <none>
  3. [machangwei@mcw7 ~]$ kubectl  describe pod mcw01dep-nginx-5dd785954d-sb8ps|grep Node:
  4. Node:         mcw9/10.0.0.139

由上找到服务所在的Node ip ,找到服务暴露出来的NodePort ,然后在外部就可以使用Node ip :NodePort来访问服务
比如这里的访问：
我在master节点访问node2节点上的服务，这个服务是node2ip,端口，映射到node2的应用docker上的80服务

  1. [machangwei@mcw7 ~]$ curl 10.0.0.139:30102
  2. <!DOCTYPE html>
  3. <html>
  4. <head>
  5. <title>Welcome to nginx!</title>
  6. <style>
  7. html { color-scheme: light dark; }
  8. body { width: 35em; margin: 0 auto;
  9. font-family: Tahoma, Verdana, Arial, sans-serif; }
  10. </style>
  11. </head>
  12. <body>
  13. <h1>Welcome to nginx!</h1>
  14. <p>If you see this page, the nginx web server is successfully installed and
  15. working. Further configuration is required.</p>
  16.  
  17. <p>For online documentation and support please refer to
  18. <a href="http://nginx.org/">nginx.org</a>.<br/>
  19. Commercial support is available at
  20. <a href="http://nginx.com/">nginx.com</a>.</p>
  21.  
  22. <p><em>Thank you for using nginx.</em></p>
  23. </body>
  24. </html>

笔记本浏览器上访问：

进入服务所在的主机节点，查看容器的ip,与之前看的容器ip等信息一致

  1. [root@mcw9 ~]$ docker ps|grep mcw01dep-nginx
  2. 374ff9c1a60e   nginx                                                "/docker-entrypoint.…"   49 minutes ago   Up 49 minutes             k8s_nginx_mcw01dep-nginx-5dd785954d-sb8ps_default_13d59a7a-c16f-44f1-b442-de7252ae4bac_0
  3. 388265797ee1   registry.aliyuncs.com/google_containers/pause:3.6    "/pause"                 49 minutes ago   Up 49 minutes             k8s_POD_mcw01dep-nginx-5dd785954d-sb8ps_default_13d59a7a-c16f-44f1-b442-de7252ae4bac_0
  4. [root@mcw9 ~]$ docker exec -it 374 hostname -i
  5. 10.244.0.4
  6. [root@mcw9 ~]$ docker exec -it 388 hostname -i
  7. OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "hostname": executable file not found in $PATH: unknown
  8. [root@mcw9 ~]$

在Nginx服务的主机上，是能直接通容器ip的

  1. [root@mcw9 ~]$ docker exec -it 374 hostname -i
  2. 10.244.0.4
  3. [root@mcw9 ~]$ docker exec -it 388 hostname -i
  4. OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "hostname": executable file not found in $PATH: unknown
  5. [root@mcw9 ~]$
  6. [root@mcw9 ~]$
  7. [root@mcw9 ~]$
  8. [root@mcw9 ~]$
  9. [root@mcw9 ~]$ ping 10.244.0.4
  10. PING 10.244.0.4 (10.244.0.4) 56(84) bytes of data.
  11. 64 bytes from 10.244.0.4: icmp_seq=1 ttl=64 time=0.256 ms
  12. 64 bytes from 10.244.0.4: icmp_seq=2 ttl=64 time=0.059 ms
  13. ^C
  14. --- 10.244.0.4 ping statistics ---
  15. 2 packets transmitted, 2 received, 0% packet loss, time 1000ms
  16. rtt min/avg/max/mdev = 0.059/0.157/0.256/0.099 ms
  17. [root@mcw9 ~]$ curl 10.244.0.4:80
  18. <!DOCTYPE html>
  19. <html>
  20. <head>
  21. <title>Welcome to nginx!</title>
  22. <style>
  23. html { color-scheme: light dark; }
  24. body { width: 35em; margin: 0 auto;
  25. font-family: Tahoma, Verdana, Arial, sans-serif; }
  26. </style>
  27. </head>
  28. <body>
  29. <h1>Welcome to nginx!</h1>
  30. <p>If you see this page, the nginx web server is successfully installed and
  31. working. Further configuration is required.</p>
  32.  
  33. <p>For online documentation and support please refer to
  34. <a href="http://nginx.org/">nginx.org</a>.<br/>
  35. Commercial support is available at
  36. <a href="http://nginx.com/">nginx.com</a>.</p>
  37.  
  38. <p><em>Thank you for using nginx.</em></p>
  39. </body>
  40. </html>
  41. [root@mcw9 ~]$

命令行部署多个副本的应用

部署多个Nginx，然后可以用上面那个例子，去做负载均衡了

  1. [machangwei@mcw7 ~]$ kubectl get deployment
  2. NAME             READY   UP-TO-DATE   AVAILABLE   AGE
  3. mcw-depcluster   3/3     3            3           92s
  4. mcw01dep-nginx   1/1     1            1           61m
  5. [machangwei@mcw7 ~]$ kubectl get replicaset
  6. NAME                        DESIRED   CURRENT   READY   AGE
  7. mcw-depcluster-547cfdc745   3         3         3       101s
  8. mcw01dep-nginx-5dd785954d   1         1         1       61m
  9. [machangwei@mcw7 ~]$ kubectl get pod
  10. NAME                              READY   STATUS    RESTARTS   AGE
  11. httpd-app                         1/1     Running   0          4h12m
  12. mcw-depcluster-547cfdc745-258sz   1/1     Running   0          118s
  13. mcw-depcluster-547cfdc745-q2785   1/1     Running   0          118s
  14. mcw-depcluster-547cfdc745-wrq74   1/1     Running   0          118s
  15. mcw01-nginx                       1/1     Running   0          63m
  16. mcw01dep-nginx-5dd785954d-sb8ps   1/1     Running   0          61m
  17. mcw1httpd-app                     1/1     Running   0          3h42m
  18. nginx-deployment                  1/1     Running   0          71m
  19. [machangwei@mcw7 ~]$ kubectl get pod --all-namespaces
  20. NAMESPACE     NAME                              READY   STATUS             RESTARTS         AGE
  21. default       httpd-app                         1/1     Running            0                4h13m
  22. default       mcw-depcluster-547cfdc745-258sz   1/1     Running            0                2m49s
  23. default       mcw-depcluster-547cfdc745-q2785   1/1     Running            0                2m49s
  24. default       mcw-depcluster-547cfdc745-wrq74   1/1     Running            0                2m49s

kubernetes运行应用1之Deployment的更多相关文章

  1. kubernetes运行应用2之DaemonSet详解

    kubernetes运行应用1之Deployment详解   查看daemonset 如下,k8s自身的 DaemonSet kube-flannel-ds和kube-proxy分别负责在每个结点上运 ...

  2. gearman kubernetes 运行

    备注: 使用的是golang 版本的实现,同时官方也提供了一个k8s 的helm 部署charts,我 没有使用这个helm,而是通过kompose 这个工具直接转换的 docker-compose ...

  3. 在kubernetes运行一个容器案例

    1. 检查kubernetes 组件是否正常运行. [root@c720120 ~]# kubectl get cs NAME                 STATUS    MESSAGE    ...

  4. (六)Kubernetes Pod控制器-ReplicaSet和Deployment和DaemonSet

    Pod控制器相关知识 控制器的必要性 自主式Pod对象由调度器调度到目标工作节点后即由相应节点上的kubelet负责监控其容器的存活状态,容器主进程崩溃后,kubelet能够自动重启相应的容器.但对出 ...

  5. kubernetes发布tomcat服务,通过deployment,service布署

    1.制作tomcat镜像 参考docker tomcat镜像制作 此处直接拉取 查看已有可镜像 先设置docker阿里源,即添加 "registry-mirrors": [&quo ...

  6. apache flink kubernetes 运行试用

    类似docker-compose 运行模式,使用的是deploy 的模式 deploy yaml 文件 deploy-k8s-yaml apiVersion: extensions/v1beta1 k ...

  7. kubernetes发布tomcat服务,通过deployment,service布署(转)

    1.制作tomcat镜像 参考docker tomcat镜像制作 此处直接拉取 查看已有可镜像 先设置docker阿里源,即添加 "registry-mirrors": [&quo ...

  8. Kubernetes 实战——升级应用（Deployment）

    一.更新运行在 Pod 内的应用程序 1. 修改 Pod 模板 将导致应用程序在一定时间内不可用 2. 修改 Service 的 Pod 选择器 需要同时运行两倍的 Pod 3. 滚动升级 应用程序需 ...

  9. kubernetes学习之service、deployment、pod的关系

    deployment根据Pod的标签关联到Pod,是为了管理pod的生命周期 service根据Pod的标签关联到pod,是为了让外部访问到pod,给pod做负载均衡 需要注意: deployment ...

随机推荐

  1. C++ 成绩排名

    1004 成绩排名 (20分)   读入 n(>)名学生的姓名.学号.成绩,分别输出成绩最高和成绩最低学生的姓名和学号. 输入格式: 每个测试输入包含 1 个测试用例,格式为 第 1 行:正整数 ...

  2. MyBatis 如何实现流式查询

    基本概念 流式查询指的是查询成功后不是返回一个集合而是返回一个迭代器,应用每次从迭代器取一条查询结果.流式查询的好处是能够降低内存使用. 如果没有流式查询,我们想要从数据库取 1000 万条记录而又没 ...

  3. Sibel Tools和Siebel Cilent的安装步骤

    关于Siebel的资料在网上是少之又少,当时安装开发工具的时候花了挺长时间的,把步骤记录了下来. 一安装win32_11gR2_client 首先要安装Oracle数据库的客户端,必须是32位,安装过 ...

  4. HongYun-ui搭建记录

    vue项目windows环境初始化 Element-ui使用 vue2 页面路由 vue SCSS 在VUE项目中使用SCSS ,对SCSS的理解和使用(简单明了) vue axios vue coo ...

  5. 【Spring Framework】spring管理自己new的对象

    使用AutowireCapableBeanFactory手动注入 使用.newInstance();创建对象的话,如果其他对象都使用Spring Autowired,还需要手动创建所有依赖的Bean: ...

  6. SQL错误总结

    ORA-00918: column ambiguously defined 异常原因: select 查询的字段在from的两张表中都存在,导致数据库无法区别需要查询的字段来自于哪张表 以下是例子 s ...

  7. 添加用户的jsp页面

    <%@ page contentType="text/html;charset=UTF-8" language="java" %><!-- H ...

  8. 测试工具_siage

    目录 一.简介 二.例子 三.参数 一.简介 Siege是一个多线程http负载测试和基准测试工具. 1.他可以查看每一个链接的状态和发送字节数 2.可以模拟不同用户进行访问 3.可以使用POST方法 ...

  9. OpenWrt之DNS设置

    目录 OpenWrt之DNS设置 0.前言 1.WAN口 2.Lan口 3.LAN口DHCP选项 4.DHCP/DNS 5.总结 参考(Thanks) 附录.DHCP OPTION OpenWrt之D ...

  10. Mac终端学习C笔记

    Mac终端自带Clang,是一个C语言.C++.Objective-C语言的轻量级编译器,也可以进行c程序编译.具体Clang和gcc区别不做详细介绍. 终端自动vi编辑器. 终端命令笔记: gcc ...