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

Typo instance group ->"InstanceGroup" 

"InstanceGroup" is written as "instance group", "instancegroup" and "InstanceGroup" in this doc.
It's a kops model, so needs to be written in same way.
This commit is contained in:
AdamDang 2018-03-09 13:17:09 +08:00 committed by GitHub
parent db01b6a01f
commit 3970776ac1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/tutorial/working-with-instancegroups.md
View File

@ -8,7 +8,7 @@ We'll assume you have a working cluster - if not, you probably want to read [how
## Changing the number of nodes
If you `kops get ig` you should see that you have instance groups for your nodes and for your master:
If you `kops get ig` you should see that you have InstanceGroups for your nodes and for your master:
```
> kops get ig
@ -17,9 +17,9 @@ master-us-central1-a Master n1-standard-1 1 1 us-central1
nodes Node n1-standard-2 2 2 us-central1
```
Let's change the number of nodes to 3. We'll edit the instancegroup configuration using `kops edit` (which
Let's change the number of nodes to 3. We'll edit the InstanceGroup configuration using `kops edit` (which
should be very familiar to you if you've used `kubectl edit`). `kops edit ig nodes` will open
the instancegroup in your editor, looking a bit like this:
the InstanceGroup in your editor, looking a bit like this:
```
apiVersion: kops/v1alpha2
@ -183,4 +183,4 @@ nodes-wbb2 Ready 5m v1.7.2 35.194.56.129 Contai
```
Next steps: learn how to perform cluster-wide operations, like [upgrading kubernetes](upgrading-kubernetes.md).
Next steps: learn how to perform cluster-wide operations, like [upgrading kubernetes](upgrading-kubernetes.md).