Deployment
Deployment 为 Pod 和 ReplicaSet 提供了一个声明式定义(declarative)方法,用来替代以前的
ReplicationController 来方便的管理应用。典型的应用场景包括:
1.定义Deployment来创建Pod和ReplicaSet
2.滚动升级和回滚应用
3.扩容和缩容
4.暂停和继续Deployment
部署一个简单的 Nginx 应用
#接口信息以及版本
apiVersion: extensions/v1beta1
#控制器
kind: Deployment
#源数据信息
metadata:
name: nginx-deployment
spec:
#副本数
replicas: 3
#模板
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.7.9
ports:
- containerPort: 80
[root@k8s-master01 ~]# kubectl apply -f deployment.yaml --record
## --record参数可以记录命令,我们可以很方便的查看每次 revision 的变化
deployment创建成功
[root@k8s-master01 ~]# kubectl get deployment
NAME READY UP-TO-DATE AVAILABLE AGE
nginx-deployment 3/3 3 3 87s
会先创建一个rs
[root@k8s-master01 ~]# kubectl get rs
NAME DESIRED CURRENT READY AGE
nginx-deployment-5754944d6c 3 3 3 118s
rs再创建pod,随机的MD5值
[root@k8s-master01 ~]# kubectl get pod
NAME READY STATUS RESTARTS AGE
frontend-f88kq 1/1 Running 0 24m
nginx-deployment-5754944d6c-96f45 1/1 Running 0 42s
nginx-deployment-5754944d6c-s457q 1/1 Running 0 42s
nginx-deployment-5754944d6c-x8qb4 1/1 Running 0 42s
查询pod对应的信息
[root@k8s-master01 ~]# kubectl get pod -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
frontend-f88kq 1/1 Running 0 28m 10.244.2.12 k8s-node02 <none> <none>
nginx-deployment-5754944d6c-96f45 1/1 Running 0 4m36s 10.244.1.11 k8s-node01 <none> <none>
nginx-deployment-5754944d6c-s457q 1/1 Running 0 4m36s 10.244.1.10 k8s-node01 <none> <none>
nginx-deployment-5754944d6c-x8qb4 1/1 Running 0 4m36s 10.244.2.1
扩容
[root@k8s-master01 ~]# kubectl scale deployment nginx-deployment --replicas 10
deployment.extensions/nginx-deployment scaled
[root@k8s-master01 ~]# kubectl get pod
NAME READY STATUS RESTARTS AGE
frontend-f88kq 1/1 Running 0 30m
nginx-deployment-5754944d6c-2fwg5 1/1 Running 0 7s
nginx-deployment-5754944d6c-6pmtp 1/1 Running 0 7s
nginx-deployment-5754944d6c-96f45 1/1 Running 0 6m41s
nginx-deployment-5754944d6c-98cbt 1/1 Running 0 7s
nginx-deployment-5754944d6c-cx99b 1/1 Running 0 7s
nginx-deployment-5754944d6c-pwlv2 1/1 Running 0 7s
nginx-deployment-5754944d6c-rgqg8 1/1 Running 0 7s
nginx-deployment-5754944d6c-s457q 1/1 Running 0 6m41s
nginx-deployment-5754944d6c-t25jt 1/1 Running 0 7s
nginx-deployment-5754944d6c-x8qb4 1/1 Running 0 6m41s
更新副本数目,是不会更新模板信息
如果集群支持 horizontal pod autoscaling 的话,还可以为Deployment设置自动扩展
[root@k8s-master01 ~]#kubectl autoscale deployment nginx-deployment --min=10 --max=15 --cpu-percent=80
更新镜像也比较简单
假如我们现在想要让 nginx pod 使用 nginx:1.9.1 的镜像来代替原来的 nginx:1.7.9 的镜像
[root@k8s-master01 ~]# kubectl get rs
NAME DESIRED CURRENT READY AGE
nginx-deployment-5754944d6c 10 10 10 9m17s
[root@k8s-master01 ~]# kubectl set image deployment/nginx-deployment nginx=nginx:1.9.1
deployment.extensions/nginx-deployment image updated
[root@k8s-master01 ~]# kubectl get rs
NAME DESIRED CURRENT READY AGE
nginx-deployment-5754944d6c 9 9 9 9m57s
nginx-deployment-7448597cd5 2 2 0 3s
可以使用 edit 命令来编辑 Deployment
[root@k8s-master01 ~]# kubectl edit deployment/nginx-deployment
更新镜像,会触发rs的创建
回滚
[root@k8s-master01 ~]# kubectl rollout undo deployment/nginx-deployment
deployment.extensions/nginx-deployment rolled back
[root@k8s-master01 ~]# kubectl get rs
NAME DESIRED CURRENT READY AGE
nginx-deployment-5754944d6c 8 8 6 12m
nginx-deployment-7448597cd5 3 3 3 2m56s
查看 rollout 的状态
[root@k8s-master01 ~]# kubectl rollout status deployment/nginx-deployment
Deployment 更新策略
Deployment 可以保证在升级时只有一定数量的 Pod 是 down 的。默认的,它会确保至少有比期望的Pod数量少一个是up状态(最多一个不可用)
Deployment 同时也可以确保只创建出超过期望数量的一定数量的 Pod。默认的,它会确保最多比期望的Pod数量多一个的 Pod 是 up 的(最多1个 surge )
未来的 Kuberentes 版本中,将从1-1变成25%-25%
[root@k8s-master01 ~]# kubectl describe deployments
Rollover(多个rollout并行)
假如您创建了一个有5个 niginx:1.7.9 replica的 Deployment,但是当还只有3个 nginx:1.7.9 的 replica 创建出来的时候您就开始更新含有5个 nginx:1.9.1 replica 的 Deployment。在这种情况下,Deployment 会立即杀掉已创建的3个 nginx:1.7.9 的 Pod,并开始创建 nginx:1.9.1 的 Pod。它不会等到所有的5个 nginx:1.7.9 的Pod 都创建完成后才开始改变航道
回退 Deployment
[root@k8s-master01 ~]#kubectl rollout undo deployment/nginx-deployment
您可以用 kubectl rollout status 命令查看 Deployment 是否完成。如果 rollout 成功完成, kubectl rollout status 将返回一个0值的 Exit Code
创建时跟上–record
[root@k8s-master01 ~]# kubectl apply -f deployment.yaml --record
更新
[root@k8s-master01 ~]# kubectl set image deployment/nginx-deployment nginx=nginx:1.91
查看历史版本记录阈值
[root@k8s-master01 ~]# kubectl rollout history deployment/nginx-deployment
deployment.extensions/nginx-deployment
REVISION CHANGE-CAUSE
1 kubectl apply --filename=deployment.yaml --record=true
2 kubectl apply --filename=deployment.yaml --record=true
[root@k8s-master01 ~]#kubectl rollout status deployments nginx-deployment
可以使用 --revision参数指定某个历史版本
[root@k8s-master01 ~]#kubectl rollout undo deployment/nginx-deployment --to-revision=2
暂停 deployment 的更新
[root@k8s-master01 ~]#kubectl rollout pause deployment/nginx-deployment
清理 Policy
您可以通过设置 .spec.revisonHistoryLimit 项来指定 deployment 最多保留多少 revision 历史记录。默认的会保留所有的 revision;如果将该项设置为0,Deployment 就不允许回退了