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

Update rolling update documentation

This commit is contained in:
John Gardiner Myers 2021-04-18 15:41:55 -07:00
parent 0187578066
commit 3fe51f2a68
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/operations/rolling-update.md
View File

@ -1,6 +1,6 @@
# Rolling Updates
Upgrading and modifying a k8s cluster usually requires the replacement of cloud instances.
Upgrading and modifying a Kubernetes cluster usually requires the replacement of cloud instances.
In order to avoid loss of service and other disruption, kOps replaces cloud instances
incrementally with a rolling update.
@ -20,11 +20,12 @@ Cloud instances are chosen to be updated (replaced) if at least one of the follo
## Order of instance groups
A rolling update will update instances from one instance group at a time. First, it will update
bastion instance groups. Next, it will update master instance groups. Finally, it will update
node instance groups.
bastion instance groups. Next, it will update master instance groups, then apiserver instance
groups. Finally, it will update node instance groups.
Within an instance group role it will update instance groups in alphabetical order.
A rolling update may be restricted to instance groups of particular roles
("Bastion", "Master", and/or "Node") with the `--instance-group-roles` flag.
("Bastion", "Master", "APIServer", and/or "Node") with the `--instance-group-roles` flag.
A rolling update may be restricted to particular instance groups with the `--instance-group` flag.
## Updating an instance group