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

Update instance_groups.md 

"instancegroup" and "instance group" appear in one sentence. It's better to use same format.
This commit is contained in:
AdamDang 2018-03-22 15:39:36 +08:00 committed by GitHub
parent 278d52d244
commit 42e3e45c8d
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/instance_groups.md
View File

@ -120,7 +120,7 @@ So the procedure is:
* (no instances need to be relaunched, so no rolling-update is needed)
## Moving from one instancegroup spanning multiple AZs to one instance group per AZ
## Moving from one instance group spanning multiple AZs to one instance group per AZ
It may be beneficial to have one IG per AZ rather than one IG spanning multiple AZs. One common example is, when you have a persistent volume claim bound to an AWS EBS Volume this volume is bound to the AZ it has been created in so any resource (e.g. a StatefulSet) depending on that volume is bound to that same AZ. In this case you have to ensure that there is at least one node running in that same AZ, which is not guaruanteed by one IG. This however can be guarantueed by one IG per AZ.