一、nginx保证有两个版本

1、查看当前容器运行nginx版本

[root@k8s-master ~]# kubectl get pod  -o wide
NAME READY STATUS RESTARTS AGE IP NODE
myweb-7w38b 1/1 Running 0 4h 172.16.10.4 k8s-node1
myweb-btflm 1/1 Running 0 4h 172.16.48.4 k8s-node2
myweb-cbt47 1/1 Running 0 4h 172.16.48.3 k8s-node2
myweb-rt3b9 1/1 Running 0 4h 172.16.10.3 k8s-node1
nginx 1/1 Running 0 6h 172.16.10.2 k8s-node1
nginx2 1/1 Running 0 5h 172.16.48.2 k8s-node2
[root@k8s-master ~]# curl -I 172.16.10.2
HTTP/1.1 200 OK
Server: nginx/1.15.8
Date: Sun, 20 Jan 2019 11:31:17 GMT
Content-Type: text/html
Content-Length: 612
Last-Modified: Tue, 25 Dec 2018 09:56:47 GMT
Connection: keep-alive
ETag: "5c21fedf-264"
Accept-Ranges: bytes

2、下载nginx1.13

[root@k8s-master ~]# docker pull nginx:1.13

3、上传到私有仓库

[root@k8s-master ~]# docker tag docker.io/nginx:latest 10.0.128.0:5000/nginx:1.15
[root@k8s-master ~]# docker tag docker.io/nginx:1.13 10.0.128.0:5000/nginx:1.13
[root@k8s-master ~]# docker push 10.0.128.0:5000/nginx:1.13
The push refers to a repository [10.0.128.0:5000/nginx]
7ab428981537: Pushed
82b81d779f83: Pushed
d626a8ad97a1: Pushed
1.13: digest: sha256:e4f0474a75c510f40b37b6b7dc2516241ffa8bde5a442bde3d372c9519c84d90 size: 948
[root@k8s-master ~]# docker push 10.0.128.0:5000/nginx:1.15
The push refers to a repository [10.0.128.0:5000/nginx]
b7efe781401d: Layer already exists
c9c2a3696080: Layer already exists
7b4e562e58dc: Layer already exists
1.15: digest: sha256:e2847e35d4e0e2d459a7696538cbfea42ea2d3b8a1ee8329ba7e68694950afd3 size: 948
[root@k8s-master ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
docker.io/registry latest 33fbbf4a24e5 2 weeks ago 24.17 MB
10.0.128.0:5000/busybox latest 3a093384ac30 2 weeks ago 1.199 MB
docker.io/busybox latest 3a093384ac30 2 weeks ago 1.199 MB
10.0.128.0:5000/nginx 1.15 7042885a156a 3 weeks ago 109.2 MB
10.0.128.0:5000/nginx latest 7042885a156a 3 weeks ago 109.2 MB
docker.io/nginx latest 7042885a156a 3 weeks ago 109.2 MB
10.0.128.0:5000/nginx 1.13 ae513a47849c 8 months ago 108.9 MB
docker.io/nginx 1.13 ae513a47849c 8 months ago 108.9 MB
10.0.128.0:5000/pod-infrastructure latest 34d3450d733b 24 months ago 205 MB
docker.io/tianyebj/pod-infrastructure latest 34d3450d733b 24 months ago 205 MB

4、私有仓库查看

[root@k8s-master ~]# ls /opt/myregistry/docker/registry/v2/repositories/nginx/_manifests/tags/
1.13 1.15 latest

二、滚动升级

1、删除所有pod和rc

[root@k8s-master ~]# kubectl get all
NAME DESIRED CURRENT READY AGE
rc/myweb 5 5 5 5h NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/kubernetes 10.254.0.1 <none> 443/TCP 21h NAME READY STATUS RESTARTS AGE
po/myweb-7w38b 1/1 Running 0 5h
po/myweb-btflm 1/1 Running 0 5h
po/myweb-cbt47 1/1 Running 0 5h
po/myweb-rt3b9 1/1 Running 0 5h
po/nginx 1/1 Running 0 6h
po/nginx2 1/1 Running 0 5h
[root@k8s-master ~]# kubectl delete pod nginx
pod "nginx" deleted

2、创建升级rc

[root@k8s-master ~]# cat myweb-rcv1.yml
apiVersion: v1
kind: ReplicationController
metadata:
name: myweb
spec:
replicas: 3
selector:
app: myweb
template:
metadata:
labels:
app: myweb
spec:
containers:
- name: myweb
image: 10.0.128.0:5000/nginx:1.13
ports:
- containerPort: 80 [root@k8s-master ~]# cat myweb-rcv2.yml
apiVersion: v1
kind: ReplicationController
metadata:
name: myweb2
spec:
replicas: 3
selector:
app: myweb2
template:
metadata:
labels:
app: myweb2
spec:
containers:
- name: myweb2
image: 10.0.128.0:5000/nginx:1.15
ports:
- containerPort: 80

3、执行升级

[root@k8s-master ~]# kubectl rolling-update myweb -f myweb-rcv2.yml --update-period=20s
Created myweb2
Scaling up myweb2 from 0 to 3, scaling down myweb from 3 to 0 (keep 3 pods available, don't exceed 4 pods)
Scaling myweb2 up to 1
Scaling myweb down to 2
Scaling myweb2 up to 2
Scaling myweb down to 1
Scaling myweb2 up to 3
Scaling myweb down to 0
Update succeeded. Deleting myweb
replicationcontroller "myweb" rolling updated to "myweb2"

4、滚动升级过程

[root@k8s-master ~]# kubectl get all
NAME DESIRED CURRENT READY AGE
rc/myweb 2 2 2 20m
rc/myweb2 2 2 2 25s NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/kubernetes 10.254.0.1 <none> 443/TCP 21h NAME READY STATUS RESTARTS AGE
po/myweb-3hg1r 1/1 Running 0 20m
po/myweb-hzxcp 1/1 Running 0 20m
po/myweb2-rhgq3 1/1 Running 0 5s
po/myweb2-xdtrp 1/1 Running 0 25s
[root@k8s-master ~]# kubectl get all
NAME DESIRED CURRENT READY AGE
rc/myweb 2 2 2 20m
rc/myweb2 2 2 2 28s NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/kubernetes 10.254.0.1 <none> 443/TCP 21h NAME READY STATUS RESTARTS AGE
po/myweb-3hg1r 1/1 Running 0 20m
po/myweb-hzxcp 1/1 Running 0 20m
po/myweb2-rhgq3 1/1 Running 0 8s
po/myweb2-xdtrp 1/1 Running 0 28s
[root@k8s-master ~]# kubectl get all
NAME DESIRED CURRENT READY AGE
rc/myweb 2 2 2 20m
rc/myweb2 2 2 2 30s NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/kubernetes 10.254.0.1 <none> 443/TCP 21h NAME READY STATUS RESTARTS AGE
po/myweb-3hg1r 1/1 Running 0 20m
po/myweb-hzxcp 1/1 Running 0 20m
po/myweb2-rhgq3 1/1 Running 0 10s
po/myweb2-xdtrp 1/1 Running 0 30s
[root@k8s-master ~]# kubectl get all
NAME DESIRED CURRENT READY AGE
rc/myweb 1 1 1 20m
rc/myweb2 2 2 2 40s NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/kubernetes 10.254.0.1 <none> 443/TCP 21h NAME READY STATUS RESTARTS AGE
po/myweb-3hg1r 1/1 Running 0 20m
po/myweb-hzxcp 1/1 Terminating 0 20m
po/myweb2-khl9t 0/1 Pending 0 0s
po/myweb2-rhgq3 1/1 Running 0 20s
po/myweb2-xdtrp 1/1 Running 0 41s
[root@k8s-master ~]# kubectl get all
NAME DESIRED CURRENT READY AGE
rc/myweb 1 1 1 20m
rc/myweb2 3 3 3 46s NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/kubernetes 10.254.0.1 <none> 443/TCP 21h NAME READY STATUS RESTARTS AGE
po/myweb-3hg1r 1/1 Running 0 20m
po/myweb2-khl9t 1/1 Running 0 6s
po/myweb2-rhgq3 1/1 Running 0 26s
po/myweb2-xdtrp 1/1 Running 0 46s
[root@k8s-master ~]# kubectl get all
NAME DESIRED CURRENT READY AGE
rc/myweb 1 1 1 20m
rc/myweb2 3 3 3 50s NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/kubernetes 10.254.0.1 <none> 443/TCP 21h NAME READY STATUS RESTARTS AGE
po/myweb-3hg1r 1/1 Running 0 20m
po/myweb2-khl9t 1/1 Running 0 10s
po/myweb2-rhgq3 1/1 Running 0 30s
po/myweb2-xdtrp 1/1 Running 0 50s
[root@k8s-master ~]# kubectl get all
NAME DESIRED CURRENT READY AGE
rc/myweb 1 1 1 20m
rc/myweb2 3 3 3 53s NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/kubernetes 10.254.0.1 <none> 443/TCP 21h NAME READY STATUS RESTARTS AGE
po/myweb-3hg1r 1/1 Running 0 20m
po/myweb2-khl9t 1/1 Running 0 13s
po/myweb2-rhgq3 1/1 Running 0 33s
po/myweb2-xdtrp 1/1 Running 0 53s
[root@k8s-master ~]# kubectl get all
NAME DESIRED CURRENT READY AGE
rc/myweb 1 1 1 20m
rc/myweb2 3 3 3 57s NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/kubernetes 10.254.0.1 <none> 443/TCP 21h NAME READY STATUS RESTARTS AGE
po/myweb-3hg1r 1/1 Running 0 20m
po/myweb2-khl9t 1/1 Running 0 17s
po/myweb2-rhgq3 1/1 Running 0 37s
po/myweb2-xdtrp 1/1 Running 0 57s
[root@k8s-master ~]# kubectl get all
NAME DESIRED CURRENT READY AGE
rc/myweb 0 0 0 21m
rc/myweb2 3 3 3 1m NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/kubernetes 10.254.0.1 <none> 443/TCP 21h NAME READY STATUS RESTARTS AGE
po/myweb2-khl9t 1/1 Running 0 23s
po/myweb2-rhgq3 1/1 Running 0 43s
po/myweb2-xdtrp 1/1 Running 0 1m
[root@k8s-master ~]# kubectl get all
NAME DESIRED CURRENT READY AGE
rc/myweb2 3 3 3 1m NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/kubernetes 10.254.0.1 <none> 443/TCP 21h NAME READY STATUS RESTARTS AGE
po/myweb2-khl9t 1/1 Running 0 29s
po/myweb2-rhgq3 1/1 Running 0 49s
po/myweb2-xdtrp 1/1 Running 0 1m

三、秒级回滚

1、执行回滚

[root@k8s-master ~]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
myweb2-khl9t 1/1 Running 0 29m 172.16.10.2 k8s-node1
myweb2-rhgq3 1/1 Running 0 29m 172.16.10.3 k8s-node1
myweb2-xdtrp 1/1 Running 0 29m 172.16.48.3 k8s-node2
[root@k8s-master ~]# kubectl rolling-update myweb2 -f myweb-rcv1.yml --update-period=10s
Created myweb
Scaling up myweb from 0 to 3, scaling down myweb2 from 3 to 0 (keep 3 pods available, don't exceed 4 pods)
Scaling myweb up to 1
Scaling myweb2 down to 2
Scaling myweb up to 2
Scaling myweb2 down to 1
Scaling myweb up to 3
Scaling myweb2 down to 0
Update succeeded. Deleting myweb2
replicationcontroller "myweb2" rolling updated to "myweb"

2、回滚过程

[root@k8s-master ~]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
myweb2-khl9t 1/1 Running 0 20m 172.16.10.2 k8s-node1
myweb2-rhgq3 1/1 Running 0 20m 172.16.10.3 k8s-node1
myweb2-xdtrp 1/1 Running 0 20m 172.16.48.3 k8s-node2
[root@k8s-master ~]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
myweb-mnf7x 1/1 Running 0 4s 172.16.48.2 k8s-node2
myweb2-khl9t 1/1 Running 0 29m 172.16.10.2 k8s-node1
myweb2-rhgq3 1/1 Running 0 29m 172.16.10.3 k8s-node1
myweb2-xdtrp 1/1 Running 0 30m 172.16.48.3 k8s-node2
[root@k8s-master ~]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
myweb-mnf7x 1/1 Running 0 6s 172.16.48.2 k8s-node2
myweb2-khl9t 1/1 Running 0 29m 172.16.10.2 k8s-node1
myweb2-rhgq3 1/1 Running 0 29m 172.16.10.3 k8s-node1
myweb2-xdtrp 1/1 Running 0 30m 172.16.48.3 k8s-node2
[root@k8s-master ~]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
myweb-mnf7x 1/1 Running 0 7s 172.16.48.2 k8s-node2
myweb2-khl9t 1/1 Running 0 29m 172.16.10.2 k8s-node1
myweb2-rhgq3 1/1 Running 0 29m 172.16.10.3 k8s-node1
myweb2-xdtrp 1/1 Running 0 30m 172.16.48.3 k8s-node2
[root@k8s-master ~]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
myweb-7m76h 1/1 Running 0 2s 172.16.10.2 k8s-node1
myweb-mnf7x 1/1 Running 0 12s 172.16.48.2 k8s-node2
myweb2-rhgq3 1/1 Running 0 29m 172.16.10.3 k8s-node1
myweb2-xdtrp 1/1 Running 0 30m 172.16.48.3 k8s-node2
[root@k8s-master ~]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
myweb-7m76h 1/1 Running 0 5s 172.16.10.2 k8s-node1
myweb-mnf7x 1/1 Running 0 15s 172.16.48.2 k8s-node2
myweb2-rhgq3 1/1 Running 0 30m 172.16.10.3 k8s-node1
myweb2-xdtrp 1/1 Running 0 30m 172.16.48.3 k8s-node2
[root@k8s-master ~]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
myweb-7m76h 1/1 Running 0 11s 172.16.10.2 k8s-node1
myweb-kzq8c 0/1 ContainerCreating 0 1s <none> k8s-node2
myweb-mnf7x 1/1 Running 0 21s 172.16.48.2 k8s-node2
myweb2-xdtrp 1/1 Running 0 30m 172.16.48.3 k8s-node2
[root@k8s-master ~]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
myweb-7m76h 1/1 Running 0 14s 172.16.10.2 k8s-node1
myweb-kzq8c 1/1 Running 0 4s 172.16.48.4 k8s-node2
myweb-mnf7x 1/1 Running 0 24s 172.16.48.2 k8s-node2
myweb2-xdtrp 1/1 Running 0 30m 172.16.48.3 k8s-node2
[root@k8s-master ~]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
myweb-7m76h 1/1 Running 0 24s 172.16.10.2 k8s-node1
myweb-kzq8c 1/1 Running 0 14s 172.16.48.4 k8s-node2
myweb-mnf7x 1/1 Running 0 34s 172.16.48.2 k8s-node2

kubernetes云平台管理实战: 滚动升级秒级回滚(六)的更多相关文章

  1. kubernetes云平台管理实战: 高级资源deployment-滚动升级(八)

    一.通过文件创建deployment 1.创建deployment文件 [root@k8s-master ~]# cat nginx_deploy.yml apiVersion: extensions ...

  2. kubernetes云平台管理实战:deployment通过标签管理pod(十)

    一.kubectl run命令拓展 1.RC创建 [root@k8s-master ~]# kubectl run web --generator=run/v1 --image=10.0.128.0: ...

  3. kubernetes云平台管理实战:如何创建deployment更好(九)

    一.文件创建带--record 1.文件 [root@k8s-master ~]# cat nginx_deploy.yml apiVersion: extensions/v1beta1 kind: ...

  4. kubernetes云平台管理实战:HPA水平自动伸缩(十一)

    一.自动伸缩 1.启动 [root@k8s-master ~]# kubectl autoscale deployment nginx-deployment --max=8 --min=2 --cpu ...

  5. kubernetes云平台管理实战: 集群部署(一)

    一.环境规划 1.架构拓扑图 2.主机规划 3.软件版本 [root@k8s-master ~]# cat /etc/redhat-release CentOS Linux release 7.4.1 ...

  6. kubernetes云平台管理实战: 自动加载到负载均衡(七)

    一.如何实现外界能访问 外界访问不了 1.启动svc [root@k8s-master ~]# cat myweb-svc.yaml apiVersion: v1 kind: Service meta ...

  7. kubernetes云平台管理实战: 故障自愈实战(四)

    一.创建实验文件 [root@k8s-master ~]# cat myweb-rc.yml apiVersion: v1 kind: ReplicationController metadata: ...

  8. kubernetes云平台管理实战: 最小的资源pod(二)

    一.pod初体验 1.编辑k8s_pod.yml文件 [root@k8s-master ~]# cat k8s_pod.yml apiVersion: v1 kind: Pod metadata: n ...

  9. kubernetes云平台管理实战: 服务发现和负载均衡(五)

    一.rc控制器常用命令 1.rc控制器信息查看 [root@k8s-master ~]# kubectl get replicationcontroller NAME DESIRED CURRENT ...

随机推荐

  1. c/c++ 拷贝控制 构造函数的问题

    拷贝控制 构造函数的问题 问题1:下面①处的代码注释掉后,就编译不过,为什么??? 问题2:但是把②处的也注释掉后,编译就过了,为什么??? 编译错误: 001.cpp: In copy constr ...

  2. Linux Shell 返回值之 PIPESTATUS

    BASH SHELL中,通常使用 $? 来获取上一条命令的返回码,对于管道中的命令,使用$?只能获取管道中最后一条命令的返回码,例如: 下面的例子 /djdjal/dajiojidksj.file是一 ...

  3. Python基础——1基础

    1.基础 输出 print(‘把子肉爱上热干面’,‘哈哈’)  # ‘,’输出为空格 输人 name = input(‘提示的内容’) /浮点除法  %.6f //地板除法  整除 %  取余 pyt ...

  4. 谈谈当代大学生学习IT技术的必要性。

    21世纪,人类社会已经从工业时代全面进入信息化时代,IT技术的发展正在影响人类的日常生活.比如,外卖平台给人们的用餐提供了更多的选择,移动支付颠覆了传统的支付方式.网购使得人们的购物更加方便,真正做到 ...

  5. web框架开发-Django组件cookie与session

    http协议的每一次都是无保存状态的请求,这会带来很多的不方便,比如,一刷新网页,或者进入该网页的其他页面,无法保存之前的登录状态.为了解决类似这样的问题,引入了会话跟踪 会话跟踪技术 1 什么是会话 ...

  6. 前端学习-基础部分-css(二)

    开始今日份整理,今日主要是CSS中很重要的一部分,就是盒模型,浮动,定位属性 1.盒模型 1.1 特性: 当对一个文档(网页)进行布局的时候,浏览器渲染引擎会根据CSS-Box模型(盒子模型)将所有元 ...

  7. Linux:Day13(上) CentOS系统启动流程

    CentOS 5和6的启动流程 Linux:kernel+rootfs kernel:进程管理.内存管理.网络管理.驱动程序.文件系统.安全功能 rootfs: glibc 库:函数集合,functi ...

  8. 初识服务发现及Consul框架的简单使用

    初识服务发现及Consul框架的简单使用   1.什么是服务发现? 服务发现组件记录了(大规模)分布式系统中所有服务的信息,人们或者其它服务可以据此找到这些服务. DNS 就是一个简单的例子. 当然, ...

  9. Oracle 查询重复索引列

    SELECT /*+ rule */ a .table_owner, a.table_name, a.index_owner, a.index_name, column_name_list, colu ...

  10. LCA-RMQ+欧拉序

    还是那一道洛谷的板子题来说吧 传送门 其实好几天之前就写了 结果dr实在是太弱了 没有那么多的精力 于是就一直咕咕咕了 哎 今天终于补上来了 LCA概念传送门 RMQ传送门 这个算法是基于RMQ和欧拉 ...