whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix some typos (#10704)

Browse Source 
* fix some typos

* s/they/there
This commit is contained in:
SataQiu
2018-10-24 06:06:24 +08:00
committed by k8s-ci-robot
parent 6705b17ebc
commit 60293a7717
10 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/blog/_posts/2018-10-08-support-for-azure-vmss.md
+2 -2
View File
@@ -89,7 +89,7 @@ acs-engine deploy --subscription-id <subscription id> \
API model file provides various configurations which acs-engine uses to create a cluster. The API model here [[5]](https://github.com/Azure/acs-engine/blob/master/examples/kubernetes-vmss/kubernetes.json) gives a good starting configuration to setup the VMSS cluster.
Once a VMSS cluster is created, here are some of the steps you can run to understand more about the cluster setup. Here is the output of kubectl get nodes from a cluster created using the above command:
Once a VMSS cluster is created, here are some of the steps you can run to understand more about the cluster setup. Here is the output of kubectl get nodes from a cluster created using the above command:
```
$ kubectl get nodes
@@ -170,7 +170,7 @@ The decision to make a scale up is based on pods which remain unscheduled and a
Cluster Autoscaler is available as an add-on with acs-engine. The following link [[15]](https://github.com/Azure/acs-engine/tree/master/examples/addons/cluster-autoscaler) has an example configuration file used to deploy autoscaler with acs-engine. The following link [[8]](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/azure/README.md) provides details on manual step by step way to do the same.
In acs-engine case we use the the regular command line to deploy:
In acs-engine case we use the regular command line to deploy:
```
acs-engine deploy --subscription-id <subscription id> \