Skip to content

Commit 1c506d7

Browse files
author
Matthew Fisher
committed
fix(quickstart): update azure quickstart docs
A couple of fixes in this commit: - prefix all environment variables with `AZURE_` for convenience - change --agent-count=1 for trial accounts - reference /home/myuser for the SSH key
1 parent db774f5 commit 1c506d7

1 file changed

Lines changed: 13 additions & 13 deletions

File tree

  • src/quickstart/provider/azure-acs

src/quickstart/provider/azure-acs/boot.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -36,10 +36,10 @@ To sign in, use a web browser to open the page https://aka.ms/devicelogin and en
3636
]
3737
```
3838

39-
The `id` field from the `az login` command is the Azure Subscription Id. This id will be used throughout the guide. As a matter of convenience, set an environment variable named `SUBSCRIPTION_ID` with the value of the id (e.g. 57849302-a9f0-4908-b300-31337a0fb205). Check the configuration by setting the active subscription with `az account set`:
39+
The `id` field from the `az login` command is the Azure Subscription Id. This id will be used throughout the guide. As a matter of convenience, set an environment variable named `AZURE_SUBSCRIPTION_ID` with the value of the id (e.g. 57849302-a9f0-4908-b300-31337a0fb205). Check the configuration by setting the active subscription with `az account set`:
4040
```
41-
$ export SUBSCRIPTION_ID=57849302-a9f0-4908-b300-31337a0fb205
42-
$ az account set --subscription="${SUBSCRIPTION_ID}"
41+
$ export AZURE_SUBSCRIPTION_ID=57849302-a9f0-4908-b300-31337a0fb205
42+
$ az account set --subscription="${AZURE_SUBSCRIPTION_ID}"
4343
```
4444

4545
## Create an ACS Kubernetes Cluster
@@ -53,24 +53,24 @@ Create an empty Azure resource group to hold the ACS Kubernetes cluster. The loc
5353
Create an environment variable to hold the resource group name:
5454

5555
```
56-
$ export RG_NAME=myresourcegroup
57-
$ export DC_LOCATION=mylocation
58-
$ az group create --name "${RG_NAME}" --location "${DC_LOCATION}"
56+
$ export AZURE_RG_NAME=myresourcegroup
57+
$ export AZURE_DC_LOCATION=mylocation
58+
$ az group create --name "${AZURE_RG_NAME}" --location "${AZURE_DC_LOCATION}"
5959
```
6060

6161
Execute the command to deploy the cluster. The `dns-prefix` and `ssh-key-value` must be replaced with your own values.
6262

6363
```
64-
$ export SERVICE_NAME=myacs
65-
$ az acs create --resource-group="${RG_NAME}" --location="${DC_LOCATION}" \
66-
--orchestrator-type=kubernetes --master-count=1 --agent-count=2 \
64+
$ export AZURE_SERVICE_NAME=myacs
65+
$ az acs create --resource-group="${AZURE_RG_NAME}" --location="${AZURE_DC_LOCATION}" \
66+
--orchestrator-type=kubernetes --master-count=1 --agent-count=1 \
6767
--agent-vm-size="Standard_D2_v2" \
6868
--admin-username="k8sadmin" \
69-
--name="${SERVICE_NAME}" --dns-prefix="mydnsprefix" \
69+
--name="${AZURE_SERVICE_NAME}" --dns-prefix="mydnsprefix" \
7070
--ssh-key-value @/home/myusername/.ssh/id_rsa.pub
7171
```
7272

73-
> Note: When `az acs create` starts, the provisioning process runs in the background by first creating a service principal named ${SERVICE_NAME} assigned appropriate permissions. After a few minutes the `az` command should return with information about the deployment created as shown below.
73+
> Note: When `az acs create` starts, the provisioning process runs in the background by first creating a service principal named ${AZURE_SERVICE_NAME} assigned appropriate permissions. After a few minutes the `az` command should return with information about the deployment created as shown below.
7474
7575
```
7676
{
@@ -152,9 +152,9 @@ az acs kubernetes install-cli
152152
Download the master kubernetes cluster configuration to the ~/.kube/config file by running the following command:
153153

154154
```console
155-
az acs kubernetes get-credentials --resource-group=$RG_NAME --name=$SERVICE_NAME
155+
az acs kubernetes get-credentials --resource-group=$AZURE_RG_NAME --name=$AZURE_SERVICE_NAME
156156
```
157-
> Note: If the cluster was provisioned using any other SSH key than `/root/.ssh/id_rsa` then the `--ssh-key-file` parameter must be used pointing to the SSH key utilized to provision the cluster.
157+
> Note: If the cluster was provisioned using any other SSH key than `/home/myusername/.ssh/id_rsa` then the `--ssh-key-file` parameter must be used pointing to the SSH key utilized to provision the cluster.
158158
159159
Verify connectivity to the new ACS Kubernetes cluster by running `kubectl cluster-info`
160160

0 commit comments

Comments
 (0)