|NO.Z.00136|——————————|CloudNative|——|KuberNetes&资源调度.V06|——|deployment.v04|扩容|缩容|
一、deployment扩容
### --- deployment扩容
~~~ 假设我们的deployment前期的业务量很小,只起了3个副本或者5个副本。
~~~ 但是随着时间的推移,当前副本已经不能支撑业务需求;
~~~ 或者说是预期内需要搞一个活动,搞活动访问量会比较大,
~~~ 需要进行扩容:# 方式一:使用kubectl工具去扩容;方式二:通过edit命令手动扩容
~~~ 推荐,kubectl命令去扩容;一般情况下只是扩容它的deployment
### --- 将deployment扩容到3个节点
[root@k8s-master01 ~]# kubectl scale --replicas=3 deploy nginx
deployment.apps/nginx scaled
### --- 查看扩容后pod的状态
~~~ DaemonSet是不支持扩容的,每个主机只有一个,
[root@k8s-master01 ~]# kubectl get po
NAME READY STATUS RESTARTS AGE
nginx-6cdd5dd489-rsf6k 1/1 Running 0 121m
nginx-6cdd5dd489-sfdzr 1/1 Running 0 119m
nginx-6cdd5dd489-wgl8p 1/1 Running 0 16s
二、deployment缩容
### --- deployment缩容为2个副本
[root@k8s-master01 ~]# kubectl scale --replicas=2 deploy nginx
deployment.apps/nginx scaled
### --- 查看pod的状态
~~~ 扩容缩容是不会产生RS的,因为他没有更改spacetimenate下的配置参数
[root@k8s-master01 ~]# kubectl get po
NAME READY STATUS RESTARTS AGE
nginx-6cdd5dd489-rsf6k 1/1 Running 0 124m
nginx-6cdd5dd489-sfdzr 1/1 Running 0 121m
nginx-6cdd5dd489-wgl8p 0/1 Terminating 0 2m29s
[root@k8s-master01 ~]# kubectl get po
NAME READY STATUS RESTARTS AGE
nginx-6cdd5dd489-rsf6k 1/1 Running 0 124m
nginx-6cdd5dd489-sfdzr 1/1 Running 0 122m
### --- 查看rs记录
~~~ 应用一:知道在多长时间内业务量会增加,提前去扩容;可以做一个计划任务去执行扩容。
~~~ 应用二:非预期之内的,
[root@k8s-master01 ~]# kubectl get rs
NAME DESIRED CURRENT READY AGE
nginx-5788dd5dcd 0 0 0 104m
nginx-5dfc8689c6 0 0 0 137m
nginx-65468bc655 0 0 0 104m
nginx-66bbc9fdc5 0 0 0 4h59m
nginx-6cdd5dd489 2 2 2 124m
nginx-6d8c8bdd68 0 0 0 104m
nginx-6f97fdfbbf 0 0 0 104m
nginx-848b8b7598 0 0 0 113m
Walter Savage Landor:strove with none,for none was worth my strife.Nature I loved and, next to Nature, Art:I warm'd both hands before the fire of life.It sinks, and I am ready to depart
——W.S.Landor
浙公网安备 33010602011771号