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

Merge pull request #6247 from rj03hou/patch-1 

Update rolling_update.md
This commit is contained in:
Kubernetes Prow Robot 2019-03-14 18:34:57 -07:00 committed by GitHub
parent b21e47e7c0 0daf792676
commit 279c1a443f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/development/rolling_update.md
View File

@ -2,6 +2,8 @@
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.
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")
`kops` executes steps 2-4 for all the masters until the masters are replaced. Then the same process is followed to replaces all nodes.