一体化监控管理平台解决方案,一体化监控管理平台的应用范围
837
2022-10-12
kubernetes核心实战(四)--- Deployments
6、Deployments(重点)
一个 Deployment 控制器为 Pods和 ReplicaSets提供描述性的更新方式。
描述 Deployment 中的 desired state,并且 Deployment 控制器以受控速率更改实际状态,以达到期望状态。可以定义 Deployments 以创建新的 ReplicaSets ,或删除现有 Deployments ,并通过新的 Deployments 使用其所有资源。
用例
以下是典型的 Deployments 用例:
创建 Deployment 以展开 ReplicaSet 。ReplicaSet 在后台创建 Pods。检查 ReplicaSet 展开的状态,查看其是否成功。
回滚到较早的 Deployment 版本,如果 Deployment 的当前状态不稳定。每次回滚都会更新 Deployment 的修改。
扩展 Deployment 以承担更多负载.
暂停 Deployment 对其 PodTemplateSpec 进行修改,然后恢复它以启动新的展开。
使用 Deployment 状态 作为卡住展开的指示器。
清理较旧的 ReplicaSets ,那些不再需要的。
1)创建 Deployment
[root@k8s-master-node1 ~/yaml/test]# vim deployments.yaml[root@k8s-master-node1 ~/yaml/test]# cat deployments.yaml apiVersion: apps/v1kind: Deploymentmetadata: name: nginx-deployment labels: app: nginxspec: replicas: 3 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: - name: nginx image: nginx:1.14.2 ports: - containerPort: 80[root@k8s-master-node1 ~/yaml/test]# [root@k8s-master-node1 ~/yaml/test]# kubectl apply -f deployments.yaml deployment.apps/nginx-deployment created[root@k8s-master-node1 ~/yaml/test]# [root@k8s-master-node1 ~/yaml/test]#
含义介绍:
在该例中:将创建名为 nginx-deployment 的 Deployment ,由 .metadata.name 字段指示。
Deployment 创建三个复制的 Pods,由 replicas 字段指示。
selector 字段定义 Deployment 如何查找要管理的 Pods。在这种情况下,只需选择在 Pod 模板(app: nginx)中定义的标签。但是,更复杂的选择规则是可能的,只要 Pod 模板本身满足规则。
说明:
matchLabels 字段是 {key,value} 的映射。单个 {key,value}在 matchLabels 映射中的值等效于 matchExpressions 的元素,其键字段是“key”,运算符为“In”,值数组仅包含“value”。所有要求,从 matchLabels 和 matchExpressions,必须满足才能匹配。
template 字段包含以下子字段:
Pod 标记为app: nginx,使用labels字段。
Pod 模板规范或 .template.spec 字段指示 Pods 运行一个容器, nginx,运行 nginx Docker Hub版本1.7.9的镜像 。
创建一个容器并使用name字段将其命名为 nginx。
查看详细的字段解释:
[root@k8s-master-node1 ~]# kubectl explain Deployment.specKIND: DeploymentVERSION: apps/v1RESOURCE: spec
查看pod
[root@k8s-master-node1 ~/yaml/test]# kubectl get pod NAME READY STATUS RESTARTS AGEingress-demo-app-694bf5d965-q4l7m 1/1 Terminating 0 23hingress-demo-app-694bf5d965-v28sl 1/1 Running 0 3m9singress-demo-app-694bf5d965-v652j 1/1 Running 0 23hnfs-client-provisioner-dc5789f74-nnk77 1/1 Running 1 (8h ago) 22hnginx-deployment-66b6c48dd5-5hhjq 1/1 Running 0 3m9snginx-deployment-66b6c48dd5-9z2n5 1/1 Running 0 3m19snginx-deployment-66b6c48dd5-llq7c 1/1 Running 0 9m10s[root@k8s-master-node1 ~/yaml/test]#
查看deployments
[root@k8s-master-node1 ~/yaml/test]# kubectl get deployments.apps NAME READY UP-TO-DATE AVAILABLE AGEingress-demo-app 2/2 2 2 23hnfs-client-provisioner 1/1 1 1 22hnginx-deployment 3/3 3 3 9m45s[root@k8s-master-node1 ~/yaml/test]#
解释说明:
检查集群中的 Deployments 时,将显示以下字段:
NAME 列出了集群中 Deployments 的名称。
DESIRED 显示应用程序的所需 副本 数,在创建 Deployment 时定义这些副本。这是 期望状态。
CURRENT显示当前正在运行的副本数。
UP-TO-DATE显示已更新以实现期望状态的副本数。
AVAILABLE显示应用程序可供用户使用的副本数。
AGE 显示应用程序运行的时间量。
查看rs
[root@k8s-master-node1 ~/yaml/test]# kubectl get replicasets.apps NAME DESIRED CURRENT READY AGEingress-demo-app-694bf5d965 2 2 2 23hnfs-client-provisioner-dc5789f74 1 1 1 23hnginx-deployment-66b6c48dd5 3 3 3 19m[root@k8s-master-node1 ~/yaml/test]#
查看pods的标签
[root@k8s-master-node1 ~/yaml/test]# kubectl get pods --show-labelsNAME READY STATUS RESTARTS AGE LABELSingress-demo-app-694bf5d965-q4l7m 1/1 Terminating 0 23h app=ingress-demo-app,pod-template-hash=694bf5d965ingress-demo-app-694bf5d965-v28sl 1/1 Running 0 15m app=ingress-demo-app,pod-template-hash=694bf5d965ingress-demo-app-694bf5d965-v652j 1/1 Running 0 23h app=ingress-demo-app,pod-template-hash=694bf5d965nfs-client-provisioner-dc5789f74-nnk77 1/1 Running 1 (8h ago) 23h app=nfs-client-provisioner,pod-template-hash=dc5789f74nginx-deployment-66b6c48dd5-48k9j 0/1 Terminating 0 21m app=nginx,pod-template-hash=66b6c48dd5nginx-deployment-66b6c48dd5-5hhjq 1/1 Running 0 15m app=nginx,pod-template-hash=66b6c48dd5nginx-deployment-66b6c48dd5-9z2n5 1/1 Running 0 15m app=nginx,pod-template-hash=66b6c48dd5nginx-deployment-66b6c48dd5-kvzft 0/1 Terminating 0 21m app=nginx,pod-template-hash=66b6c48dd5nginx-deployment-66b6c48dd5-llq7c 1/1 Running 0 21m app=nginx,pod-template-hash=66b6c48dd5[root@k8s-master-node1 ~/yaml/test]#
2)更新回滚 Deployment
命令行行升级使用镜像
[root@k8s-master-node1 ~/yaml/test]# kubectl get deployments -o wideNAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTORingress-demo-app 2/2 2 2 23h whoami traefik/whoami:v1.6.1 app=ingress-demo-appnfs-client-provisioner 1/1 1 1 23h nfs-client-provisioner registry.cn-hangzhou.aliyuncs.com/lfy_k8s_images/nfs-subdir-external-provisioner:v4.0.2 app=nfs-client-provisionernginx-deployment 3/3 3 3 18m nginx nginx:1.14.2 app=nginx[root@k8s-master-node1 ~/yaml/test]# [root@k8s-master-node1 ~/yaml/test]# kubectl --record deployment.apps/nginx-deployment set image deployment.v1.apps/nginx-deployment nginx=nginx:1.20.1Flag --record has been deprecated, --record will be removed in the futuredeployment.apps/nginx-deployment image updateddeployment.apps/nginx-deployment image updated[root@k8s-master-node1 ~/yaml/test]# [root@k8s-master-node1 ~/yaml/test]# kubectl get deployments -o wideNAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTORingress-demo-app 2/2 2 2 23h whoami traefik/whoami:v1.6.1 app=ingress-demo-appnfs-client-provisioner 1/1 1 1 23h nfs-client-provisioner registry.cn-hangzhou.aliyuncs.com/lfy_k8s_images/nfs-subdir-external-provisioner:v4.0.2 app=nfs-client-provisionernginx-deployment 3/3 1 3 24m nginx nginx:1.20.1 app=nginx[root@k8s-master-node1 ~/yaml/test]#
yaml方式修改镜像
[root@k8s-master-node1 ~/yaml/test]# kubectl edit deployments.apps nginx-deploymentEdit cancelled, no changes made.[root@k8s-master-node1 ~/yaml/test]#
查看更新过程
[root@k8s-master-node1 ~/yaml/test]# kubectl rollout status deployment.v1.apps/nginx-deploymentWaiting for deployment "nginx-deployment" rollout to finish: 1 out of 3 new replicas have been updated...Waiting for deployment "nginx-deployment" rollout to finish: 1 out of 3 new replicas have been updated...Waiting for deployment "nginx-deployment" rollout to finish: 1 out of 3 new replicas have been updated...Waiting for deployment "nginx-deployment" rollout to finish: 2 out of 3 new replicas have been updated...Waiting for deployment "nginx-deployment" rollout to finish: 2 out of 3 new replicas have been updated...Waiting for deployment "nginx-deployment" rollout to finish: 2 out of 3 new replicas have been updated...Waiting for deployment "nginx-deployment" rollout to finish: 1 old replicas are pending termination...Waiting for deployment "nginx-deployment" rollout to finish: 1 old replicas are pending termination...deployment "nginx-deployment" successfully rolled out[root@k8s-master-node1 ~/yaml/test]#
查看详细信息
[root@k8s-master-node1 ~/yaml/test]# kubectl describe deploymentsName: ingress-demo-appNamespace: defaultCreationTimestamp: Tue, 16 Nov 2021 13:28:26 +0800Labels: app=ingress-demo-appAnnotations: deployment.kubernetes.io/revision: 1Selector: app=ingress-demo-appReplicas: 2 desired | 2 updated | 2 total | 2 available | 0 unavailableStrategyType: RollingUpdateMinReadySeconds: 0RollingUpdateStrategy: 25% max unavailable, 25% max surgePod Template: Labels: app=ingress-demo-app Containers: whoami: Image: traefik/whoami:v1.6.1 Port: 80/TCP Host Port: 0/TCP Environment:
3) Deployment历史记录
查看历史
[root@k8s-master-node1 ~/yaml/test]# kubectl rollout history deployment.v1.apps/nginx-deploymentdeployment.apps/nginx-deployment REVISION CHANGE-CAUSE1
回滚到上次
[root@k8s-master-node1 ~/yaml/test]# kubectl rollout undo deployment.v1.apps/nginx-deploymentdeployment.apps/nginx-deployment rolled back[root@k8s-master-node1 ~/yaml/test]# kubectl rollout status deployment.v1.apps/nginx-deploymentWaiting for deployment "nginx-deployment" rollout to finish: 1 old replicas are pending termination...Waiting for deployment "nginx-deployment" rollout to finish: 1 old replicas are pending termination...deployment "nginx-deployment" successfully rolled out[root@k8s-master-node1 ~/yaml/test]#
回滚到指定版本
[root@k8s-master-node1 ~/yaml/test]# kubectl rollout undo deployment.v1.apps/nginx-deployment --to-revision=3deployment.apps/nginx-deployment rolled back[root@k8s-master-node1 ~/yaml/test]# kubectl rollout status deployment.v1.apps/nginx-deploymentWaiting for deployment "nginx-deployment" rollout to finish: 2 out of 3 new replicas have been updated...Waiting for deployment "nginx-deployment" rollout to finish: 2 out of 3 new replicas have been updated...Waiting for deployment "nginx-deployment" rollout to finish: 2 out of 3 new replicas have been updated...Waiting for deployment "nginx-deployment" rollout to finish: 1 old replicas are pending termination...Waiting for deployment "nginx-deployment" rollout to finish: 1 old replicas are pending termination...deployment "nginx-deployment" successfully rolled out[root@k8s-master-node1 ~/yaml/test]#
4)缩放 Deployment
扩容到十个pod
[root@k8s-master-node1 ~/yaml/test]# kubectl scale deployment.v1.apps/nginx-deployment --replicas=10deployment.apps/nginx-deployment scaled[root@k8s-master-node1 ~/yaml/test]# [root@k8s-master-node1 ~/yaml/test]# kubectl get deployments.appsNAME READY UP-TO-DATE AVAILABLE AGEingress-demo-app 0/2 2 0 24hnfs-client-provisioner 0/1 1 0 23hnginx-deployment 5/10 10 5 45m[root@k8s-master-node1 ~/yaml/test]#
假设启用水平自动缩放 Pod在集群中,可以为 Deployment 设置自动缩放器,并选择最小和最大 要基于现有 Pods 的 CPU 利用率运行的 Pods。
[root@k8s-master-node1 ~/yaml/test]# kubectl autoscale deployment.v1.apps/nginx-deployment --min=10 --max=15 --cpu-percent=80horizontalpodautoscaler.autoscaling/nginx-deployment autoscaled[root@k8s-master-node1 ~/yaml/test]# [root@k8s-master-node1 ~/yaml/test]#
https://blog.csdn.net/qq_33921750
https://my.oschina.net/u/3981543
https://zhihu.com/people/chen-bu-yun-2
https://segmentfault.com/u/hppyvyv6/articles
https://juejin.cn/user/3315782802482007
https://space.bilibili.com/352476552/article
https://cloud.tencent.com/developer/column/93230
知乎、CSDN、开源中国、思否、掘金、哔哩哔哩、腾讯云
发表评论
暂时没有评论,来抢沙发吧~