Skip to content
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.

Commit

Permalink
docs(Azure): remove service principal steps
Browse files Browse the repository at this point in the history
These and JQ are no longer needed since the latest AZ cli automatically creates a service principal as a part of az acs create.  Also existing service principal steps in this doc changed.
  • Loading branch information
dtzar committed Jan 26, 2017
1 parent 01ac5dd commit 4eea426
Showing 1 changed file with 1 addition and 26 deletions.
27 changes: 1 addition & 26 deletions src/quickstart/provider/azure-acs/boot.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,6 @@

4. SSH Key - This is used to deploy the cluster. [This URL helps to create SSH keys compatible with Linux VMs on Azure](https://docs.microsoft.com/azure/virtual-machines/virtual-machines-linux-mac-create-ssh-keys)

5. jq - to parse the JSON responses from the CLI. [jq download page](https://stedolan.github.io/jq/)

## Configure the Azure CLI

After installing the CLI, log in to an Azure Account by typing `az login`. Take the code offered, enter it into the text box at [https://aka.ms/devicelogin](https://aka.ms/devicelogin), and login using an Azure account which has ownership or contributor permissions over at least one subscription.
Expand Down Expand Up @@ -44,27 +42,6 @@ $ export SUBSCRIPTION_ID=57849302-a9f0-4908-b300-31337a0fb205
$ az account set --subscription="${SUBSCRIPTION_ID}"
```

## Create an Azure Service Principal

Next, create an Azure Service Principal that will be used to provision the ACS Kubernetes Cluster. Service Principals are entities that have permission to create resources in an Azure Subscription. New Service Principals must be given a unique name, a role, and an Azure subscription that the Service Principal may modify.

```
$ export SP_JSON=`az ad sp create-for-rbac -n="http://acsk8sdeis" --role="Contributor" --scopes="/subscriptions/${SUBSCRIPTION_ID}"`
$ export SP_NAME=`echo $SP_JSON | jq -r '.name'`
$ export SP_PASS=`echo $SP_JSON | jq -r '.password'`
$ echo $SP_JSON
```

This should display an output similar to this. `jq` has also automatically extracted these values for use in the creation of the cluster.
```
{
"appId": "58b21231-3dd7-4546-bd37-9df88812331f",
"name": "http://workflow-on-acs",
"password": "349d4728-438a-52a5-ad25-a740aa0bd240",
"tenant": "891a9ddc-477a-4620-8f21-db22ffd3ffea"
}
```

## Create an ACS Kubernetes Cluster

Azure supports two methods to build an ACS Kubernetes cluster, through the Azure Web Portal (UI) or using the Azure command line (CLI). Choose one of the two paths:
Expand All @@ -86,16 +63,14 @@ Execute the command to deploy the cluster. The `dns-prefix` and `ssh-key-value`
```
$ export SERVICE_NAME=myacs
$ az acs create --resource-group="${RG_NAME}" --location="${DC_LOCATION}" \
--service-principal="${SP_NAME}" \
--client-secret="${SP_PASS}" \
--orchestrator-type=kubernetes --master-count=1 --agent-count=2 \
--agent-vm-size="Standard_D2_v2" \
--admin-username="k8sadmin" \
--name="${SERVICE_NAME}" --dns-prefix="mydnsprefix" \
--ssh-key-value @/home/myusername/.ssh/id_rsa.pub
```

> Note: When `az acs create` starts, the provisioning process runs entirely silent in the background. After a few minutes the `az` command should return with information about the deployment created as shown below.
> Note: When `az acs create` starts, the provisioning process runs in the background by first creating a service principal and then waiting for AAD role to propagate. After a few minutes the `az` command should return with information about the deployment created as shown below.
```
{
Expand Down

0 comments on commit 4eea426

Please sign in to comment.