• pod控制器

    pod控制器详解

    1.ReplicaSet(RS)

    ReplicaSet的主要作用是保证一定数量的pod正常运行，它会持续监听这些Pod的运行状态，一旦Pod发生故障，就会重启或重建。同时它还支持对pod数量的扩缩容和镜像版本的升降级

    它的资源清单文件有：

    1. apiVersion: apps/v1 # 版本号
    2. kind: ReplicaSet # 类型       
    3. metadata: # 元数据
    4.   name: # rs名称 
    5.   namespace: # 所属命名空间 
    6.   labels: #标签
    7.     controller: rs
    8. spec: # 详情描述
    9.   replicas: 3 # 副本数量
    10.   selector: # 选择器，通过它指定该控制器管理哪些pod
    11.     matchLabels:      # Labels匹配规则
    12.       app: nginx-pod
    13.     matchExpressions: # Expressions匹配规则
    14.       - {key: app, operator: In, values: [nginx-pod]}
    15.   template: # 模板，当副本数量不足时，会根据下面的模板创建pod副本
    16.     metadata:
    17.       labels:
    18.         app: nginx-pod
    19.     spec:
    20.       containers:
    21.       - name: nginx
    22.         image: nginx:1.17.1
    23.         ports:
    24.         - containerPort: 80

    创建ReplicaSet

    1. 创建yaml文件
    2. apiVersion: apps/v1
    3. kind: ReplicaSet   
    4. metadata:
    5.   name: pc-replicaset
    6.   namespace: dev
    7. spec:
    8.   replicas: 3
    9.   selector: 
    10.     matchLabels:
    11.       app: nginx-pod
    12.   template:
    13.     metadata:
    14.       labels:
    15.         app: nginx-pod
    16.     spec:
    17.       containers:
    18.       - name: nginx
    19.         image: nginx:1.17.1
    20.  
    21.  
    22.  
    23. //创建rs
    24. [root@master ~]# kubectl create -f pc-replicaset.yaml
    25. replicaset.apps/pc-replicaset created
    26.  
    27. //查看rs
    28. [root@master ~]# kubectl get rs pc-replicaset -n dev -o wide
    29. NAME          DESIRED   CURRENT READY AGE   CONTAINERS   IMAGES             SELECTOR
    30. pc-replicaset 3         3       3     22s   nginx        nginx:1.17.1       app=nginx-pod
    31.  
    32.  
    33. //查看控制器创建出来的pod
    34. [root@master ~]# kubectl get pod -n dev
    35. NAME                          READY   STATUS    RESTARTS   AGE
    36. pc-replicaset-6vmvt   1/1     Running   0          54s
    37. pc-replicaset-fmb8f   1/1     Running   0          54s
    38. pc-replicaset-snrk2   1/1     Running   0          54s
    39.

    扩缩容

    1. //修改rs的副本数量
    2. [root@master ~]# vim pc-replicaset.yaml
    3. spec:
    4.   replicas: 6
    5. [root@master ~]# kubectl edit rs pc-replicaset -n dev
    6. replicaset.apps/pc-replicaset edited
    7.  
    8. //查看pod
    9. [root@master ~]# kubectl get pods -n dev
    10. NAME                          READY   STATUS    RESTARTS   AGE
    11. pc-replicaset-6vmvt   1/1     Running   0          114m
    12. pc-replicaset-cftnp   1/1     Running   0          10s
    13. pc-replicaset-fjlm6   1/1     Running   0          10s
    14. pc-replicaset-fmb8f   1/1     Running   0          114m
    15. pc-replicaset-s2whj   1/1     Running   0          10s
    16. pc-replicaset-snrk2   1/1     Running   0          114m
    17.  
    18. //直接使用命令配置
    19. [root@master ~]# kubectl scale rs pc-replicaset --replicas=2 -n dev
    20. replicaset.apps/pc-replicaset scaled
    21.  
    22. //查看pod
    23. [root@master ~]# kubectl get pods -n dev
    24. NAME                       READY   STATUS        RESTARTS   AGE
    25. pc-replicaset-6vmvt   0/1     Terminating   0          118m
    26. pc-replicaset-cftnp   0/1     Terminating   0          4m17s
    27. pc-replicaset-fjlm6   0/1     Terminating   0          4m17s
    28. pc-replicaset-fmb8f   1/1     Running       0          118m
    29. pc-replicaset-s2whj   0/1     Terminating   0          4m17s
    30. pc-replicaset-snrk2   1/1     Running       0          118m
    31.  
    32. //稍等片刻，就只剩下2个了
    33. [root@master ~]# kubectl get pods -n dev
    34. NAME                       READY   STATUS    RESTARTS   AGE
    35. pc-replicaset-fmb8f   1/1     Running   0          119m
    36. pc-replicaset-snrk2   1/1     Running   0          119m

    镜像升级

    1. //编辑rs的容器镜像
    2. [root@master ~]# vim pc-replicaset.yaml
    3. image: nginx:1.17.2
    4. [root@master ~]# kubectl edit rs pc-replicaset -n dev
    5. replicaset.apps/pc-replicaset edited
    6.  
    7. //再次查看，发现镜像版本已经改变
    8. [root@master ~]# kubectl get rs -n dev -o wide
    9. NAME                DESIRED  CURRENT   READY   AGE    CONTAINERS   IMAGES        
    10. pc-replicaset       2        2         2       140m   nginx         nginx:1.17.2  
    11.  
    12. //同样也可使用命令完成
    13. [root@master ~]# kubectl set image rs pc-replicaset nginx=nginx:1.17.1  -n dev
    14. replicaset.apps/pc-replicaset image updated
    15.  
    16. //再次查看，发现镜像版本已经变更了
    17. [root@master ~]# kubectl get rs -n dev -o wide
    18. NAME                 DESIRED  CURRENT   READY   AGE    CONTAINERS   IMAGES            
    19. pc-replicaset        2        2         2       145m   nginx        nginx:1.17.1

    2.Deployment(Deploy)

    Deployment主要功能有下面几个：

    • 支持ReplicaSet的所有功能
    • 支持发布的停止、继续
    • 支持滚动升级和回滚版本

    可配置的Deployment的资源清单文件有：

    1. apiVersion: apps/v1 # 版本号
    2. kind: Deployment # 类型       
    3. metadata: # 元数据
    4.   name: # rs名称 
    5.   namespace: # 所属命名空间 
    6.   labels: #标签
    7.     controller: deploy
    8. spec: # 详情描述
    9.   replicas: 3 # 副本数量
    10.   revisionHistoryLimit: 3 # 保留历史版本
    11.   paused: false # 暂停部署，默认是false
    12.   progressDeadlineSeconds: 600 # 部署超时时间（s），默认是600
    13.   strategy: # 策略
    14.     type: RollingUpdate # 滚动更新策略
    15.     rollingUpdate: # 滚动更新
    16.       maxSurge: 30% # 最大额外可以存在的副本数，可以为百分比，也可以为整数
    17.       maxUnavailable: 30% # 最大不可用状态的 Pod 的最大值，可以为百分比，也可以为整数
    18.   selector: # 选择器，通过它指定该控制器管理哪些pod
    19.     matchLabels:      # Labels匹配规则
    20.       app: nginx-pod
    21.     matchExpressions: # Expressions匹配规则
    22.       - {key: app, operator: In, values: [nginx-pod]}
    23.   template: # 模板，当副本数量不足时，会根据下面的模板创建pod副本
    24.     metadata:
    25.       labels:
    26.         app: nginx-pod
    27.     spec:
    28.       containers:
    29.       - name: nginx
    30.         image: nginx:1.17.1
    31.         ports:
    32.         - containerPort: 80

    创建deployment

    1. //创建yaml文件
    2. apiVersion: apps/v1
    3. kind: Deployment      
    4. metadata:
    5.   name: pc-deployment
    6.   namespace: dev
    7. spec: 
    8.   replicas: 3
    9.   selector:
    10.     matchLabels:
    11.       app: nginx-pod
    12.   template:
    13.     metadata:
    14.       labels:
    15.         app: nginx-pod
    16.     spec:
    17.       containers:
    18.       - name: nginx
    19.         image: nginx:1.17.1
    20.  
    21.  
    22. //创建deployment
    23. [root@master ~]# kubectl create -f pc-deployment.yaml --record=true
    24. deployment.apps/pc-deployment created
    25.  
    26. //查看deployment
    27. UP-TO-DATE 最新版本的pod的数量
    28. AVAILABLE  当前可用的pod的数量
    29. [root@master ~]# kubectl get deploy pc-deployment -n dev
    30. NAME            READY   UP-TO-DATE   AVAILABLE   AGE
    31. pc-deployment   3/3     3            3           15s
    32.  
    33. //查看rs
    34. [root@k8s-master01 ~]# kubectl get rs -n dev
    35. NAME                       DESIRED   CURRENT   READY   AGE
    36. pc-deployment-6696798b78   3         3         3       23s
    37.  
    38. //查看pod
    39. [root@k8s-master01 ~]# kubectl get pods -n dev
    40. NAME                             READY   STATUS    RESTARTS   AGE
    41. pc-deployment-6696798b78-d2c8n   1/1     Running   0          107s
    42. pc-deployment-6696798b78-smpvp   1/1     Running   0          107s
    43. pc-deployment-6696798b78-wvjd8   1/1     Running   0          107s
    44.  
    45.

    扩缩容

    1. //变更副本数量为5个
    2. [root@master ~]# kubectl scale deploy pc-deployment --replicas=5  -n dev
    3. deployment.apps/pc-deployment scaled
    4.  
    5. //查看deployment
    6. [root@master ~]# kubectl get deploy pc-deployment -n dev
    7. NAME            READY   UP-TO-DATE   AVAILABLE   AGE
    8. pc-deployment   5/5     5            5           2m
    9.  
    10. //查看pod
    11. [root@master ~]#  kubectl get pods -n dev
    12. NAME                             READY   STATUS    RESTARTS   AGE
    13. pc-deployment-6696798b78-d2c8n   1/1     Running   0          4m19s
    14. pc-deployment-6696798b78-jxmdq   1/1     Running   0          94s
    15. pc-deployment-6696798b78-mktqv   1/1     Running   0          93s
    16. pc-deployment-6696798b78-smpvp   1/1     Running   0          4m19s
    17. pc-deployment-6696798b78-wvjd8   1/1     Running   0          4m19s
    18.  
    19. //deployment的副本数量
    20. [root@master ~]# vim pc-deployment.yaml
    21. spec:replicas: 4
    22. [root@master ~]# kubectl edit deploy pc-deployment -n dev
    23. deployment.apps/pc-deployment edited
    24.  
    25. # 查看pod
    26. [root@master ~]# kubectl get pods -n dev
    27. NAME                             READY   STATUS    RESTARTS   AGE
    28. pc-deployment-6696798b78-d2c8n   1/1     Running   0          5m23s
    29. pc-deployment-6696798b78-jxmdq   1/1     Running   0          2m38s
    30. pc-deployment-6696798b78-smpvp   1/1     Running   0          5m23s
    31. pc-deployment-6696798b78-wvjd8   1/1     Running   0          5m23s

    镜像更新

    deployment支持两种更新策略:重建更新和滚动更新,可以通过strategy指定策略类型,支持两个属性

    滚动更新：

    1.编辑pc-deployment.yaml,在spec节点下添加更新策略

    1. spec:
    2.   strategy: # 策略
    3.     type: RollingUpdate # 滚动更新策略
    4.     rollingUpdate:
    5.       maxSurge: 25% 
    6.       maxUnavailable: 25%

    2.创建deploy进行验证

    1. //变更镜像
    2. [root@k8s-master01 ~]# kubectl set image deployment pc-deployment nginx=nginx:1.17.3 -n dev 
    3. deployment.apps/pc-deployment image updated
    4.  
    5. //查看升级过程
    6. [root@master ~]# kubectl get pods -n dev -w
    7. NAME                           READY   STATUS    RESTARTS   AGE
    8. pc-deployment-c848d767-8rbzt   1/1     Running   0          31m
    9. pc-deployment-c848d767-h4p68   1/1     Running   0          31m
    10. pc-deployment-c848d767-hlmz4   1/1     Running   0          31m
    11. pc-deployment-c848d767-rrqcn   1/1     Running   0          31m
    12.  
    13. pc-deployment-966bf7f44-226rx   0/1     Pending             0          0s
    14. pc-deployment-966bf7f44-226rx   0/1     ContainerCreating   0          0s
    15. pc-deployment-966bf7f44-226rx   1/1     Running             0          1s
    16. pc-deployment-c848d767-h4p68    0/1     Terminating         0          34m
    17.  
    18. pc-deployment-966bf7f44-cnd44   0/1     Pending             0          0s
    19. pc-deployment-966bf7f44-cnd44   0/1     ContainerCreating   0          0s
    20. pc-deployment-966bf7f44-cnd44   1/1     Running             0          2s
    21. pc-deployment-c848d767-hlmz4    0/1     Terminating         0          34m
    22.  
    23. pc-deployment-966bf7f44-px48p   0/1     Pending             0          0s
    24. pc-deployment-966bf7f44-px48p   0/1     ContainerCreating   0          0s
    25. pc-deployment-966bf7f44-px48p   1/1     Running             0          0s
    26. pc-deployment-c848d767-8rbzt    0/1     Terminating         0          34m
    27.  
    28. pc-deployment-966bf7f44-dkmqp   0/1     Pending             0          0s
    29. pc-deployment-966bf7f44-dkmqp   0/1     ContainerCreating   0          0s
    30. pc-deployment-966bf7f44-dkmqp   1/1     Running             0          2s
    31. pc-deployment-c848d767-rrqcn    0/1     Terminating         0          34m
    32.

    至此，新版本的pod创建完毕，旧版本的pod销毁完毕
    中间过程是滚动进行的，也就是边销毁边创建

    版本回退

    deployment支持版本升级过程中的暂停、继续功能以及版本回退等诸多功能，下面具体来看.

    kubectl rollout： 版本升级相关功能，支持下面的选项：

    • status 显示当前升级状态
    • history 显示 升级历史记录
    • pause 暂停版本升级过程
    • resume 继续已经暂停的版本升级过程
    • restart 重启版本升级过程
    • undo 回滚到上一级版本（可以使用--to-revision回滚到指定版本）
    1. //查看当前升级版本的状态
    2. [root@master ~]# kubectl rollout status deploy pc-deployment -n dev
    3. deployment "pc-deployment" successfully rolled out
    4.  
    5. //查看升级历史记录
    6. [root@master ~]# kubectl rollout history deploy pc-deployment -n dev
    7. deployment.apps/pc-deployment
    8. REVISION  CHANGE-CAUSE
    9. 1         <none>
    10. 2         <none>
    11. 3         <none>
    12. //可以发现有三次版本记录，说明完成过两次升级
    13.  
    14.  
    15. //版本回退
    16. [root@master ~]# kubectl rollout undo deployment pc-deployment --to-revision1
    17. deployment.apps/pc-deployment rolled back
    18.  
    19. //查看发现，通过nginx镜像版本可以发现到了第一版
    20. [root@master ~]# kubectl get deploy -n dev -o wide
    21. NAME            READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS   IMAGES         
    22. pc-deployment   4/4     4            4           74m   nginx        nginx:1.17.1   
    23.  
    24. //
    25. [root@master ~]# kubectl get rs -n dev
    26. NAME                       DESIRED   CURRENT   READY   AGE
    27. pc-deployment-6696798b78   2         2         2       24h
    28. pc-deployment-966bf7f44    0         0         0       24h
    29. pc-deployment-c848d767     0         0         0       24h

    金丝雀发布

    Deployment控制器支持控制更新过程中的控制，如“暂停(pause)”或“继续(resume)”更新操作。

    比如有一批新的Pod资源创建完成后立即暂停更新过程，此时，仅存在一部分新版本的应用，主体部分还是旧的版本。然后，再筛选一小部分的用户请求路由到新版本的Pod应用，继续观察能否稳定地按期望的方式运行。确定没问题之后再继续完成余下的Pod资源滚动更新，否则立即回滚更新操作。这就是所谓的金丝雀发布

    1. //更新deployment的版本，并配置暂停deployment
    2. [root@master ~]#  kubectl set image deploy pc-deployment nginx=nginx:1.17.4 -n dev && kubectl rollout pause deployment pc-deployment  -n dev
    3. deployment.apps/pc-deployment image updated
    4. deployment.apps/pc-deployment paused
    5.  
    6. //观察更新状态
    7. [root@master ~]# kubectl rollout status deploy pc-deployment -n dev　
    8. Waiting for deployment "pc-deployment" rollout to finish: 2 out of 4 new replicas have been updated...
    9.  
    10.  
    11. [root@master ~]# kubectl get rs -n dev -o wide
    12. NAME                       DESIRED   CURRENT   READY   AGE     CONTAINERS   IMAGES         
    13. pc-deployment-5d89bdfbf9   3         3         3       19m     nginx        nginx:1.17.1   
    14. pc-deployment-675d469f8b   0         0         0       14m     nginx        nginx:1.17.2   
    15. pc-deployment-6c9f56fcfb   2         2         2       3m16s   nginx        nginx:1.17.4   
    16. [root@master ~]# kubectl get pods -n dev
    17. NAME                             READY   STATUS    RESTARTS   AGE
    18. pc-deployment-5d89bdfbf9-rj8sq   1/1     Running   0          7m33s
    19. pc-deployment-5d89bdfbf9-ttwgg   1/1     Running   0          7m35s
    20. pc-deployment-5d89bdfbf9-v4wvc   1/1     Running   0          7m34s
    21. pc-deployment-6c9f56fcfb-996rt   1/1     Running   0          3m31s
    22. pc-deployment-6c9f56fcfb-j2gtj   1/1     Running   0          3m31s
    23.  
    24. //确保更新的pod没问题了，继续更新
    25. [root@master ~]# kubectl rollout resume deploy pc-deployment -n dev
    26. deployment.apps/pc-deployment resumed
    27.  
    28. //查看最后的更新情况
    29. [root@master ~]# kubectl get rs -n dev -o wide
    30. NAME                       DESIRED   CURRENT   READY   AGE     CONTAINERS   IMAGES         
    31. pc-deployment-5d89bdfbf9   0         0         0       21m     nginx        nginx:1.17.1   
    32. pc-deployment-675d469f8b   0         0         0       16m     nginx        nginx:1.17.2   
    33. pc-deployment-6c9f56fcfb   4         4         4       5m11s   nginx        nginx:1.17.4   
    34.  
    35. [root@master ~]# kubectl get pods -n dev
    36. NAME                             READY   STATUS    RESTARTS   AGE
    37. pc-deployment-6c9f56fcfb-7bfwh   1/1     Running   0          37s
    38. pc-deployment-6c9f56fcfb-996rt   1/1     Running   0          5m27s
    39. pc-deployment-6c9f56fcfb-j2gtj   1/1     Running   0          5m27s
    40. pc-deployment-6c9f56fcfb-rf84v   1/1     Running   0          37s

    删除Deployment

    1. //删除deployment，其下的rs和pod也将被删除
    2. [root@master ~]# kubectl delete -f pc-deployment.yaml
    3. deployment.apps "pc-deployment" deleted

    3.Horizontal Pod Autoscaler(HPA)

    Kubernetes期望可以实现通过监测Pod的使用情况，实现pod数量的自动调整，于是就产生了Horizontal Pod Autoscaler（HPA）这种控制器

    1.安装metrics-server

    1. 安装metrics-server
    2. //安装git
    3. [root@master ~]# yum -y install git
    4.  
    5. //获取metrics-server, 注意使用的版本
    6. [root@master ~]# git clone -b v0.3.6 https://github.com/kubernetes-incubator/metrics-server
    7.  
    8. //修改deployment, 注意修改的是镜像和初始化参数
    9. [root@master ~]# cd /root/metrics-server/deploy/1.8+/
    10. [root@master 1.8+]#  vim metrics-server-deployment.yaml	
    11. 按如下yaml文件进行修改
    12.  
    13. //安装metrics-server
    14. [root@master 1.8+]# kubectl apply -f ./
    15.  
    16. //查看pod运行情况
    17. [root@master 1.8+]# kubectl get pod -n kube-system
    18. NAME                                    READY   STATUS    RESTARTS   AGE
    19. metrics-server-9c7dc6fdc-5589z          1/1     Running   0          9s
    20.  
    21. //使用kubectl top node查看资源使用情况
    22. [root@master 1.8+]# kubectl top node
    23. NAME            CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%   
    24. k8s-master-01   170m         8%     1022Mi          35%       
    25. k8s-node-01     45m          2%     367Mi           12%       
    26. k8s-node-02     39m          1%     286Mi           9%        
    27.  
    28. [root@master 1.8+]# kubectl top pod -n kube-system
    29. NAME                                    CPU(cores)   MEMORY(bytes)   
    30. coredns-7d7778b79-dlvkp                 3m           15Mi            
    31. coredns-7d7778b79-sdxkg                 3m           15Mi            
    32.  
    33.  
    34. //至此,metrics-server安装完成
    35.  
    36.  
    37.  
    38. 修改metrics-server-deployment.yaml文件
    39.  
    40. ---
    41. apiVersion: v1
    42. kind: ServiceAccount
    43. metadata:
    44.   name: metrics-server
    45.   namespace: kube-system
    46. ---
    47. apiVersion: apps/v1
    48. kind: Deployment
    49. metadata:
    50.   name: metrics-server
    51.   namespace: kube-system
    52.   labels:
    53.     k8s-app: metrics-server
    54. spec:
    55.   selector:
    56.     matchLabels:
    57.       k8s-app: metrics-server
    58.   template:
    59.     metadata:
    60.       name: metrics-server
    61.       labels:
    62.         k8s-app: metrics-server
    63.     spec:
    64.       hostNetwork: true
    65.       serviceAccountName: metrics-server
    66.       volumes:
    67.       # mount in tmp so we can safely use from-scratch images and/or read-only containers
    68.       - name: tmp-dir
    69.         emptyDir: {}
    70.       containers:
    71.       - name: metrics-server
    72.         image: registry.cn-hangzhou.aliyuncs.com/google_containers/metrics-server-amd64:v0.3.6
    73.         imagePullPolicy: Always
    74.         args:
    75.         - --kubelet-insecure-tls
    76.         - --kubelet-preferred-address-types=InternalIP,Hostname,InternalDNS,ExternalDNS,ExternalIP
    77.         volumeMounts:
    78.         - name: tmp-dir
    79.           mountPath: /tmp
    80.  
    81.  
    82.

    2. 准备创建deployment和servie

    1. //创建deployment
    2. kind: Deployment
    3. apiVersion: apps/v1
    4. metadata:
    5.   namespace: dev
    6.   name: nginx
    7. spec:
    8.   selector:
    9.     matchLabels:
    10.       app: nginx
    11.   template:
    12.     metadata:
    13.       labels:
    14.         app: nginx
    15.     spec:
    16.       containers:
    17.         - name: nginx
    18.           image: nginx
    19.           resources:
    20.             requests:
    21.               cpu: 10m
    22.             limits:
    23.               cpu: 10m
    24. ---
    25. //创建service
    26. kind: Service
    27. apiVersion: v1
    28. metadata:
    29.   name: nginx
    30.   namespace: dev
    31. spec:
    32.   ports:
    33.     - port: 80
    34.       targetPort: 80
    35.       nodePort: 30080
    36.   selector:
    37.     app: nginx
    38.   type: NodePort
    39.  
    40.  
    41.  
    42. //创建deployment和servie
    43. [root@master ~]# kubectl create -f nginx.yaml 
    44. deployment.apps/nginx created
    45. service/nginx created
    46.  
    47. //查看
    48. [root@master ~]# kubectl get deployment,pod,svc -n dev
    49. NAME                    READY   UP-TO-DATE   AVAILABLE   AGE
    50. deployment.apps/nginx   1/1     1            1           48s
    51.  
    52. NAME                        READY   STATUS    RESTARTS   AGE
    53. pod/nginx-d657f44c6-dltql   1/1     Running   0          48s
    54.  
    55. NAME            TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE
    56. service/nginx   NodePort   10.96.239.131   <none>        80:30080/TCP   48s

    3. 部署HPA

    1. 创建pc-hpa.yaml文件
    2. kind: HorizontalPodAutoscaler
    3. apiVersion: autoscaling/v2beta1
    4. metadata:
    5.   name: nginx
    6.   namespace: dev
    7. spec:
    8.   maxReplicas: 10    # 最大pod数量
    9.   minReplicas: 1     # 最小pod数量
    10.   scaleTargetRef:    # 指定要控制的nginx信息
    11.     kind: Deployment
    12.     name: nginx
    13.     apiVersion: apps/v1
    14.   metrics:
    15.     - type: Resource
    16.       resource:
    17.         name: cpu
    18.         targetAverageUtilization: 3   # CPU使用率指标
    19.  
    20.  
    21. //创建hpa
    22. [root@master ~]#  kubectl create -f pc-hpa.yaml
    23. horizontalpodautoscaler.autoscaling/pc-hpa created
    24.  
    25. //查看hpa
    26. [root@master ~]# kubectl get hpa -n dev
    27. NAME    REFERENCE          TARGETS   MINPODS   MAXPODS   REPLICAS   AGE
    28. nginx   Deployment/nginx   0%/3%     1         10        1          18s

    4. 测试

    1. hpa变化
    2. [root@master ~]# kubectl get hpa -n dev -w
    3. NAME    REFERENCE          TARGETS   MINPODS   MAXPODS   REPLICAS   AGE
    4. nginx   Deployment/nginx   0%/3%     1         10        1          7m19s
    5. nginx   Deployment/nginx   110%/3%   1         10        1          7m30s
    6. nginx   Deployment/nginx   110%/3%   1         10        4          7m45s
    7. nginx   Deployment/nginx   110%/3%   1         10        8          8m
    8. nginx   Deployment/nginx   110%/3%   1         10        10         8m15s
    9. nginx   Deployment/nginx   100%/3%   1         10        10         8m30s
    10. nginx   Deployment/nginx   0%/3%     1         10        10         9m31s
    11. nginx   Deployment/nginx   0%/3%     1         10        10         14m
    12. nginx   Deployment/nginx   0%/3%     1         10        10         15m
    13.  
    14.  
    15. deployment变化
    16. [root@master ~]# kubectl get deployment -n dev -w
    17. NAME    READY   UP-TO-DATE   AVAILABLE   AGE
    18. nginx   1/1     1            1           10m
    19. nginx   1/4     1            1           11m
    20. nginx   1/4     1            1           11m
    21. nginx   1/4     1            1           11m
    22. nginx   1/4     4            1           11m
    23. nginx   1/8     4            1           11m
    24. nginx   1/8     4            1           11m
    25. nginx   1/8     4            1           11m
    26. nginx   1/8     8            1           11m
    27. nginx   1/10    8            1           11m
    28. nginx   1/10    8            1           11m
    29. nginx   1/10    8            1           11m
    30. nginx   1/10    10           1           11m
    31. nginx   2/10    10           2           11m
    32. nginx   3/10    10           3           11m
    33. nginx   4/10    10           4           12m
    34. nginx   5/10    10           5           12m
    35. nginx   6/10    10           6           12m
    36. nginx   7/10    10           7           12m
    37. nginx   8/10    10           8           12m
    38. nginx   9/10    10           9           12m
    39. nginx   10/10   10           10          13m
    40. nginx   10/1    10           10          18m
    41. nginx   10/1    10           10          18m
    42. nginx   1/1     1            1           18m
    43.  
    44.  
    45. pod变化
    46. [root@master ~]# kubectl get pods -n dev -w
    47. NAME                    READY   STATUS    RESTARTS   AGE
    48. nginx-d657f44c6-dltql   1/1     Running   0          11m
    49. nginx-d657f44c6-dbtbq   0/1     Pending   0          0s
    50. nginx-d657f44c6-5hxf6   0/1     Pending   0          0s
    51. nginx-d657f44c6-f8mw6   0/1     Pending   0          0s
    52. nginx-d657f44c6-dbtbq   0/1     ContainerCreating   0          0s
    53. nginx-d657f44c6-5hxf6   0/1     ContainerCreating   0          0s
    54. nginx-d657f44c6-f8mw6   0/1     ContainerCreating   0          0s
    55. nginx-d657f44c6-ctgtc   0/1     Pending             0          0s
    56. nginx-d657f44c6-n6h6d   0/1     Pending             0          0s
    57. nginx-d657f44c6-jhlp5   0/1     Pending             0          0s
    58. nginx-d657f44c6-brdnf   0/1     Pending             0          0s
    59. nginx-d657f44c6-ctgtc   0/1     ContainerCreating   0          0s
    60. nginx-d657f44c6-n6h6d   0/1     ContainerCreating   0          0s
    61. nginx-d657f44c6-jhlp5   0/1     ContainerCreating   0          0s
    62. nginx-d657f44c6-brdnf   0/1     ContainerCreating   0          0s
    63. nginx-d657f44c6-28jcf   0/1     Pending             0          0s
    64. nginx-d657f44c6-7wff5   0/1     Pending             0          0s
    65. nginx-d657f44c6-28jcf   0/1     ContainerCreating   0          0s
    66. nginx-d657f44c6-7wff5   0/1     ContainerCreating   0          0s
    67. nginx-d657f44c6-5hxf6   1/1     Running             0          38s
    68. nginx-d657f44c6-jhlp5   1/1     Running             0          35s
    69. nginx-d657f44c6-f8mw6   1/1     Running             0          64s
    70. nginx-d657f44c6-ctgtc   1/1     Running             0          50s
    71. nginx-d657f44c6-dbtbq   1/1     Running             0          72s
    72. nginx-d657f44c6-28jcf   1/1     Running             0          52s
    73. nginx-d657f44c6-brdnf   1/1     Running             0          84s
    74. nginx-d657f44c6-n6h6d   1/1     Running             0          99s
    75. nginx-d657f44c6-7wff5   1/1     Running             0          95s
    76.  
    77. nginx-d657f44c6-5hxf6   1/1     Terminating         0          7m46s
    78. nginx-d657f44c6-28jcf   1/1     Terminating         0          7m16s
    79. nginx-d657f44c6-brdnf   1/1     Terminating         0          7m31s
    80. nginx-d657f44c6-n6h6d   1/1     Terminating         0          7m31s
    81. nginx-d657f44c6-7wff5   1/1     Terminating         0          7m16s
    82. nginx-d657f44c6-ctgtc   1/1     Terminating         0          7m31s
    83. nginx-d657f44c6-jhlp5   1/1     Terminating         0          7m31s
    84. nginx-d657f44c6-f8mw6   1/1     Terminating         0          7m46s
    85. nginx-d657f44c6-dbtbq   1/1     Terminating         0          7m46s
    86.  
    87. nginx-d657f44c6-n6h6d   0/1     Terminating         0          7m32s
    88. nginx-d657f44c6-7wff5   0/1     Terminating         0          7m17s

    DaemonSet(DS)

    DaemonSet类型的控制器可以保证在集群中的每一台（或指定）节点上都运行一个副本。一般适用于日志收集、节点监控等场景。也就是说，如果一个Pod提供的功能是节点级别的（每个节点都需要且只需要一个），那么这类Pod就适合使用DaemonSet类型的控制器创建

    DaemonSet控制器的特点：

    • 每当向集群中添加一个节点时，指定的 Pod 副本也将添加到该节点上

    • 当节点从集群中移除时，Pod 也就被垃圾回收了

    可配置的DaemonSet的资源清单文件

    1. apiVersion: apps/v1 # 版本号
    2. kind: DaemonSet # 类型       
    3. metadata: # 元数据
    4.   name: # rs名称 
    5.   namespace: # 所属命名空间 
    6.   labels: #标签
    7.     controller: daemonset
    8. spec: # 详情描述
    9.   revisionHistoryLimit: 3 # 保留历史版本
    10.   updateStrategy: # 更新策略
    11.     type: RollingUpdate # 滚动更新策略
    12.     rollingUpdate: # 滚动更新
    13.       maxUnavailable: 1 # 最大不可用状态的 Pod 的最大值，可以为百分比，也可以为整数
    14.   selector: # 选择器，通过它指定该控制器管理哪些pod
    15.     matchLabels:      # Labels匹配规则
    16.       app: nginx-pod
    17.     matchExpressions: # Expressions匹配规则
    18.       - {key: app, operator: In, values: [nginx-pod]}
    19.   template: # 模板，当副本数量不足时，会根据下面的模板创建pod副本
    20.     metadata:
    21.       labels:
    22.         app: nginx-pod
    23.     spec:
    24.       containers:
    25.       - name: nginx
    26.         image: nginx:1.17.1
    27.         ports:
    28.         - containerPort: 80

    创建pc-daemonset.yaml文件

    1. apiVersion: apps/v1
    2. kind: DaemonSet      
    3. metadata:
    4.   name: pc-daemonset
    5.   namespace: dev
    6. spec: 
    7.   selector:
    8.     matchLabels:
    9.       app: nginx-pod
    10.   template:
    11.     metadata:
    12.       labels:
    13.         app: nginx-pod
    14.     spec:
    15.       containers:
    16.       - name: nginx
    17.         image: nginx:1.17.1

    创建pod观察效果

    1. //创建daemonset
    2. [root@master ~]# kubectl create -f pc-daemonset.yaml 
    3. daemonset.apps/pc-daemonset created
    4.  
    5. //查看daemonset
    6. [root@master ~]# kubectl get ds -n dev -o wide
    7. NAME           DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE   CONTAINERS   IMAGES         SELECTOR
    8. pc-daemonset   2         2         0       2            0           <none>          20s   nginx        nginx:1.17.1   app=nginx-pod
    9.  
    10. //查看pod,发现在每个Node上都运行一个pod
    11. [root@master ~]# kubectl get pods -n dev -o wide
    12. NAME                    READY   STATUS    RESTARTS   AGE    IP           NODE          NOMINATED NODE   READINESS GATES
    13. pc-daemonset-46jp5      1/1     Running   0          103s   10.244.1.7   k8s-node-01   <none>           <none>
    14. pc-daemonset-xqd5w      1/1     Running   0          103s   10.244.2.8   k8s-node-02   <none>           <none>
    15.  
    16. //删除daemonset
    17. [root@master ~]# kubectl delete -f pc-daemonset.yaml 
    18. daemonset.apps "pc-daemonset" deleted

    Job

    ob，主要用于负责批量处理(一次要处理指定数量任务)短暂的一次性(每个任务仅运行一次就结束)任务。Job特点如下：

    • 当Job创建的pod执行成功结束时，Job将记录成功结束的pod数量

    • 当成功结束的pod达到指定的数量时，Job将完成执行

    可配置的Job资源清单文件有

    1. apiVersion: batch/v1 # 版本号
    2. kind: Job # 类型       
    3. metadata: # 元数据
    4.   name: # rs名称 
    5.   namespace: # 所属命名空间 
    6.   labels: #标签
    7.     controller: job
    8. spec: # 详情描述
    9.   completions: 1 # 指定job需要成功运行Pods的次数。默认值: 1
    10.   parallelism: 1 # 指定job在任一时刻应该并发运行Pods的数量。默认值: 1
    11.   activeDeadlineSeconds: 30 # 指定job可运行的时间期限，超过时间还未结束，系统将会尝试进行终止。
    12.   backoffLimit: 6 # 指定job失败后进行重试的次数。默认是6
    13.   manualSelector: true # 是否可以使用selector选择器选择pod，默认是false
    14.   selector: # 选择器，通过它指定该控制器管理哪些pod
    15.     matchLabels:      # Labels匹配规则
    16.       app: counter-pod
    17.     matchExpressions: # Expressions匹配规则
    18.       - {key: app, operator: In, values: [counter-pod]}
    19.   template: # 模板，当副本数量不足时，会根据下面的模板创建pod副本
    20.     metadata:
    21.       labels:
    22.         app: counter-pod
    23.     spec:
    24.       restartPolicy: Never # 重启策略只能设置为Never或者OnFailure
    25.       containers:
    26.       - name: counter
    27.         image: busybox:1.30
    28.         command: ["bin/sh","-c","for i in 9 8 7 6 5 4 3 2 1; do echo $i;sleep 2;done"]

    创建pc-job.yaml

    1. apiVersion: batch/v1
    2. kind: Job      
    3. metadata:
    4.   name: pc-job
    5.   namespace: dev
    6. spec:
    7.   manualSelector: true
    8.   selector:
    9.     matchLabels:
    10.       app: counter-pod
    11.   template:
    12.     metadata:
    13.       labels:
    14.         app: counter-pod
    15.     spec:
    16.       restartPolicy: Never
    17.       containers:
    18.       - name: counter
    19.         image: busybox:1.30
    20.         command: ["bin/sh","-c","for i in 9 8 7 6 5 4 3 2 1; do echo $i;sleep 3;done"]

    创建pod观察效果

    1. //创建job
    2. [root@master ~]# kubectl create -f pc-job.yaml
    3. job.batch/pc-job created
    4.  
    5. //查看job
    6. [root@master ~]# kubectl get job -n dev -o wide  -w
    7. NAME     COMPLETIONS   DURATION   AGE   CONTAINERS   IMAGES         SELECTOR
    8. pc-job   0/1           0s         0s    counter      busybox:1.30   app=counter-pod
    9. pc-job   1/1           28s        28s   counter      busybox:1.30   app=counter-pod
    10.  
    11. //通过观察pod状态可以看到，pod在运行完毕任务后，就会变成Completed状态
    12. [root@master ~]# kubectl get pods -n dev -w
    13. NAME                    READY   STATUS    RESTARTS   AGE
    14. pc-job-6wk89            1/1     Running             0          1s
    15. pc-job-6wk89            0/1     Completed           0          28s
    16.  
    17. //直接更新是不行的，对于同一个Job，这是不可变参数
    18. [root@master ~]# kubectl delete -f pc-job.yaml
    19. job.batch "pc-job" deleted
    20.  
    21.  
    22. //然后重新运行job，观察效果，此时会发现，job会每次运行3个pod，总共执行了3个pod
    23. [root@master ~]# kubectl create -f pc-job.yaml
    24. job.batch/pc-job created
    25.  
    26. [root@master ~]# kubectl get pods -n dev -w
    27. NAME                    READY   STATUS    RESTARTS   AGE
    28. nginx-d657f44c6-dltql   1/1     Running   0          105m
    29. pc-job-6r2hl            0/1     Pending   0          0s
    30. pc-job-6r2hl            0/1     Pending   0          0s
    31. pc-job-zk9qn            0/1     Pending   0          0s
    32. pc-job-hzf49            0/1     Pending   0          0s
    33. pc-job-hzf49            0/1     Pending   0          0s
    34. pc-job-zk9qn            0/1     Pending   0          0s
    35. pc-job-6r2hl            0/1     ContainerCreating   0          0s
    36. pc-job-zk9qn            0/1     ContainerCreating   0          0s
    37. pc-job-hzf49            0/1     ContainerCreating   0          0s
    38. pc-job-hzf49            1/1     Running             0          3s
    39. pc-job-6r2hl            1/1     Running             0          3s
    40. pc-job-hzf49            0/1     Completed           0          29s
    41. pc-job-6r2hl            0/1     Completed           0          29s
    42. pc-job-zk9qn            1/1     Running             0          44s
    43. pc-job-zk9qn            0/1     Completed           0          72s
    44.  
    45. //删除job
    46. [root@master ~]# kubectl delete -f pc-job.yaml 
    47. job.batch "pc-job" deleted

    关于job的重启策略，有以下说明：

    1.如果指定为OnFailure，则job会在pod出现故障时重启容器，而不是创建pod，failed次数不变

    2.如果指定为Never，则job会在pod出现故障时创建新的pod，并且故障pod不会消失，也不会重启，failed次数加1

    3.如果指定为Always的话，就意味着一直重启，意味着job任务会重复去执行了，当然不对，所以不能设置为Always

    CronJob(CJ)

    CronJob控制器以Job控制器资源为其管控对象，并借助它管理pod资源对象，Job控制器定义的作业任务在其控制器资源创建之后便会立即执行，但CronJob可以以类似于Linux操作系统的 周期性计划任务的方式 控制其运行 时间点 及 重复运行 的方式。也就是说，CronJob可以在特定的时间点(反复的)去运行job任务
     

    可配置的CronJob的资源清单文件有

    1. apiVersion: batch/v1beta1 # 版本号
    2. kind: CronJob 	# 类型       
    3. metadata: 	# 元数据
    4.   name: 	# rs名称 
    5.   namespace: 	# 所属命名空间 
    6.   labels: 	#标签
    7.     controller: cronjob
    8. spec: 	# 详情描述
    9.   schedule: 	# cron格式的作业调度运行时间点,用于控制任务在什么时间执行
    10.   concurrencyPolicy: 	# 并发执行策略，用于定义前一次作业运行尚未完成时是否以及如何运行后一次的作业
    11.   failedJobHistoryLimit: 	# 为失败的任务执行保留的历史记录数，默认为1
    12.   successfulJobHistoryLimit:	 # 为成功的任务执行保留的历史记录数，默认为3
    13.   startingDeadlineSeconds: 	# 启动作业错误的超时时长
    14.   jobTemplate: 		# job控制器模板，用于为cronjob控制器生成job对象;下面其实就是job的定义
    15.     metadata:
    16.     spec:
    17.       completions: 1
    18.       parallelism: 1
    19.       activeDeadlineSeconds: 30
    20.       backoffLimit: 6
    21.       manualSelector: true
    22.       selector:
    23.         matchLabels:
    24.           app: counter-pod
    25.         matchExpressions: 规则
    26.           - {key: app, operator: In, values: [counter-pod]}
    27.       template:
    28.         metadata:
    29.           labels:
    30.             app: counter-pod
    31.         spec:
    32.           restartPolicy: Never 
    33.           containers:
    34.           - name: counter
    35.             image: busybox:1.30
    36.             command: ["bin/sh","-c","for i in 9 8 7 6 5 4 3 2 1; do echo $i;sleep 20;done"]

    创建pc-cronjob.yaml

    1. apiVersion: batch/v1beta1
    2. kind: CronJob
    3. metadata:
    4.   name: pc-cronjob
    5.   namespace: dev
    6.   labels:
    7.     controller: cronjob
    8. spec:
    9.   schedule: "*/1 * * * *"
    10.   jobTemplate:
    11.     metadata:
    12.     spec:
    13.       template:
    14.         spec:
    15.           restartPolicy: Never
    16.           containers:
    17.           - name: counter
    18.             image: busybox:1.30
    19.             command: ["bin/sh","-c","for i in 9 8 7 6 5 4 3 2 1; do echo $i;sleep 3;done"]

    创建cronjob

    1. //创建cronjob
    2. [root@master ~]# kubectl create -f pc-job.yaml
    3. job.batch/pc-job created
    4.  
    5. //查看cronjob
    6. [root@master ~]# kubectl get cronjobs -n dev
    7. NAME         SCHEDULE      SUSPEND   ACTIVE   LAST SCHEDULE   AGE
    8. pc-cronjob   */1 * * * *   False     0        <none>          2s
    9.  
    10. //查看job
    11. [root@master ~]# kubectl get jobs -n dev
    12. NAME                  COMPLETIONS   DURATION   AGE
    13. pc-cronjob-27143584   1/1           27s        2m20s
    14. pc-cronjob-27143585   1/1           28s        80s
    15. pc-cronjob-27143586   0/1           20s        20s
    16.  
    17. //查看pod
    18. [root@master ~]# kubectl get pods -n dev
    19. NAME                        READY   STATUS      RESTARTS   AGE
    20. nginx-d657f44c6-dltql       1/1     Running     0          127m
    21. pc-cronjob-27143584-ntw6x   0/1     Completed   0          2m3s
    22. pc-cronjob-27143585-66f9p   0/1     Completed   0          63s
    23. pc-cronjob-27143586-sqnsj   1/1     Running     0          3s
    24.  
    25. //删除cronjob
    26. [root@master ~]# kubectl delete -f pc-cronjob.yaml 
    27. cronjob.batch "pc-cronjob" deleted

  • 相关阅读:
    学生HTML个人网页作业作品下载 动漫主题网页设计制作 大学生个人网站作业模板 dreamweaver简单个人网页制作
    Java中的实体类为什么要 implements Serializable?
    RISCV学习（2）玄铁C910处理器体验
    pandas dataframe drop函数
    上机实验一 顺序表的基本操作和简单程序 西安石油大学数据结构
    unity项目加密（比如到指定时间，项目打不开）
    项目管理软件应该具备哪些功能
    c++ - 第12节 - 模板进阶
    最佳联盟营销软件解决方案：简化你的联盟管理
    子路由的配置方法
  • 原文地址：https://blog.csdn.net/qq_58328312/article/details/126862004