kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update docs/development/rolling_update.md 

Co-Authored-By: rj03hou <rj03hou@gmail.com>
This commit is contained in:
Pharb 2018-12-31 17:25:52 +08:00 committed by GitHub
parent 15d45d8b41
commit 0daf792676
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/development/rolling_update.md
View File

@ -2,7 +2,7 @@
Upgrading and modifying a k8s cluster often requires the replacement of nodes. To not cause loss of service and other disruptions a kops uses a functionality call rolling updates. Rolling a cluster is the replacement of the masters and nodes with new cloud instances.
Before rolling update, kops will check whether the instance in the ig need to be update, so when you just update nodes, the master will not roll, when you rolling be interrupted, you run again, will not roll the new instance.
When starting the rolling update, kops will check each instance in the instance group if it needs to be updated, so when you just update nodes, the master will not be updated. When your rolling update is interrupted and you run another rolling update, instances that have been updated before will not be updated again.
![Rolling Update Diagram](/docs/development/images/rolling-update.png?raw=true "Rolling Updates Diagram")