https://wiki.linuxsa.org/index.php?action=history&feed=atom&title=Rolling_Update_%E6%BB%9A%E5%8A%A8%E6%9B%B4%E6%96%B0
Rolling Update 滚动更新 - 版本历史
2026-04-23T11:09:07Z
本wiki上该页面的版本历史
MediaWiki 1.43.1
https://wiki.linuxsa.org/index.php?title=Rolling_Update_%E6%BB%9A%E5%8A%A8%E6%9B%B4%E6%96%B0&diff=944&oldid=prev
Evan：导入1个版本
2019-10-14T13:52:34Z
<p>导入1个版本</p>
<p><b>新页面</b></p><div>=更新=<br />
<pre><br />
** 7.1 practice<br />
<br />
evan@k8s-master:~$ kubectl get deployment httpd -o wide <br />
NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR<br />
httpd 2/3 3 2 68s httpd httpd:2.2.31 run=httpd<br />
evan@k8s-master:~$ kubectl get pod <br />
\NAME READY STATUS RESTARTS AGE<br />
httpd-5ddb558f47-2pmhw 1/1 Running 0 78s<br />
httpd-5ddb558f47-rwbhc 1/1 Running 0 78s<br />
httpd-5ddb558f47-xtfb2 0/1 ImagePullBackOff 0 78s<br />
<br />
evan@k8s-master:~$ kubectl get pod <br />
NAME READY STATUS RESTARTS AGE<br />
httpd-5ddb558f47-2pmhw 1/1 Running 0 12m<br />
httpd-5ddb558f47-rwbhc 1/1 Running 0 12m<br />
httpd-5ddb558f47-xtfb2 1/1 Running 0 12m<br />
<br />
evan@k8s-master:~$ kubectl get deployment httpd -o wide <br />
NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR<br />
httpd 3/3 3 3 12m httpd httpd:2.2.31 run=httpd<br />
<br />
<br />
evan@k8s-master:~$ kubectl get replicaset -o wide <br />
NAME DESIRED CURRENT READY AGE CONTAINERS IMAGES SELECTOR<br />
httpd-5ddb558f47 3 3 3 13m httpd httpd:2.2.31 pod-template-hash=5ddb558f47,run=httpd<br />
<br />
将配置文件中 httpd:2.2.31 替换为 httpd:2.2.32，再次执行 kubectl apply<br />
<br />
---- ------ ---- ---- -------<br />
Normal ScalingReplicaSet 16m deployment-controller Scaled up replica set httpd-5ddb558f47 to 3<br />
Normal ScalingReplicaSet 99s deployment-controller Scaled up replica set httpd-8bdffc6d8 to 1<br />
Normal ScalingReplicaSet 99s deployment-controller Scaled down replica set httpd-5ddb558f47 to 2<br />
Normal ScalingReplicaSet 98s deployment-controller Scaled up replica set httpd-8bdffc6d8 to 2<br />
Normal ScalingReplicaSet 6s deployment-controller Scaled down replica set httpd-5ddb558f47 to 1<br />
Normal ScalingReplicaSet 6s deployment-controller Scaled up replica set httpd-8bdffc6d8 to 3<br />
<br />
<br />
---- ------ ---- ---- -------<br />
Normal ScalingReplicaSet 16m deployment-controller Scaled up replica set httpd-5ddb558f47 to 3<br />
Normal ScalingReplicaSet 99s deployment-controller Scaled up replica set httpd-8bdffc6d8 to 1<br />
Normal ScalingReplicaSet 99s deployment-controller Scaled down replica set httpd-5ddb558f47 to 2<br />
Normal ScalingReplicaSet 98s deployment-controller Scaled up replica set httpd-8bdffc6d8 to 2<br />
Normal ScalingReplicaSet 6s deployment-controller Scaled down replica set httpd-5ddb558f47 to 1<br />
Normal ScalingReplicaSet 6s deployment-controller Scaled up replica set httpd-8bdffc6d8 to 3<br />
</pre><br />
<br />
=回滚=<br />
<pre><br />
** 7.2 回滚<br />
ubectl apply 每次更新应用时 Kubernetes 都会记录下当前的配置，保存为一个 revision（版次），这样就可以回滚到某个特定 revision。<br />
<br />
默认配置下，Kubernetes 只会保留最近的几个 revision，可以在 Deployment 配置文件中通过 revisionHistoryLimit 属性增加 revision 数量。<br />
<br />
下面实践回滚功能。应用有如下三个配置文件 httpd.v1.yml，httpd.v2.yml 和 httpd.v3.yml，分别对应不同的 httpd 镜像 2.4.16，2.4.17 和 2.4.18：<br />
<br />
evan@k8s-master:~$ kubectl apply -f httpd.v1.yml --record <br />
deployment.extensions/httpd created<br />
evan@k8s-master:~$ kubectl get deployment httpd -o wide <br />
NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR<br />
httpd 0/3 3 0 3s httpd httpd:2.4.16 run=httpd<br />
evan@k8s-master:~$ kubectl apply -f httpd.v2.yml --record <br />
deployment.extensions/httpd configured<br />
evan@k8s-master:~$ kubectl get deployment httpd -o wide <br />
NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR<br />
httpd 0/3 2 0 30s httpd httpd:2.4.18 run=httpd<br />
evan@k8s-master:~$ kubectl apply -f httpd.v3.yml --record <br />
deployment.extensions/httpd configured<br />
evan@k8s-master:~$ kubectl get deployment httpd -o wide <br />
NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR<br />
httpd 0/3 2 0 39s httpd httpd:2.4.18 run=httpd<br />
<br />
--record 的作用是将当前命令记录到 revision 记录中，这样我们就可以知道每个 revison 对应的是哪个配置文件。通过 kubectl rollout history deployment httpd 查看 revison 历史记录<br />
<br />
evan@k8s-master:~$ kubectl rollout history deployment httpd<br />
deployment.extensions/httpd <br />
REVISION CHANGE-CAUSE<br />
1 kubectl apply --filename=httpd.v1.yml --record=true<br />
2 kubectl apply --filename=httpd.v3.yml --record=true<br />
3 kubectl apply --filename=httpd.v2.yml --record=true<br />
<br />
<br />
evan@k8s-master:~$ kubectl get deployment httpd -o wide <br />
NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR<br />
httpd 2/3 2 2 3m9s httpd httpd:2.4.17 run=httpd<br />
<br />
evan@k8s-master:~$ kubectl rollout undo deployment httpd --to-revision=1<br />
deployment.extensions/httpd rolled back<br />
evan@k8s-master:~$ kubectl get deployment httpd -o wide <br />
NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR<br />
httpd 2/3 3 2 3m36s httpd httpd:2.4.16 run=httpd<br />
<br />
evan@k8s-master:~$ kubectl rollout history deployment httpd<br />
deployment.extensions/httpd <br />
REVISION CHANGE-CAUSE<br />
2 kubectl apply --filename=httpd.v3.yml --record=true<br />
3 kubectl apply --filename=httpd.v2.yml --record=true<br />
4 kubectl apply --filename=httpd.v1.yml --record=true<br />
<br />
<br />
<br />
<br />
</pre><br />
<br />
=see also=<br />
https://www.cnblogs.com/CloudMan6/p/8543006.html<br />
<br />
https://www.cnblogs.com/CloudMan6/p/8553331.html<br />
<br />
[[category:k8s]]</div>
Evan