Skip to content

Commit 4eea426

Browse files
David Tesardtzar
authored andcommitted
docs(Azure): remove service principal steps
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.
1 parent 01ac5dd commit 4eea426

1 file changed

Lines changed: 1 addition & 26 deletions

File tree

  • src/quickstart/provider/azure-acs

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

Lines changed: 1 addition & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,6 @@
1111

1212
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)
1313

14-
5. jq - to parse the JSON responses from the CLI. [jq download page](https://stedolan.github.io/jq/)
15-
1614
## Configure the Azure CLI
1715

1816
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.
@@ -44,27 +42,6 @@ $ export SUBSCRIPTION_ID=57849302-a9f0-4908-b300-31337a0fb205
4442
$ az account set --subscription="${SUBSCRIPTION_ID}"
4543
```
4644

47-
## Create an Azure Service Principal
48-
49-
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.
50-
51-
```
52-
$ export SP_JSON=`az ad sp create-for-rbac -n="http://acsk8sdeis" --role="Contributor" --scopes="/subscriptions/${SUBSCRIPTION_ID}"`
53-
$ export SP_NAME=`echo $SP_JSON | jq -r '.name'`
54-
$ export SP_PASS=`echo $SP_JSON | jq -r '.password'`
55-
$ echo $SP_JSON
56-
```
57-
58-
This should display an output similar to this. `jq` has also automatically extracted these values for use in the creation of the cluster.
59-
```
60-
{
61-
"appId": "58b21231-3dd7-4546-bd37-9df88812331f",
62-
"name": "http://workflow-on-acs",
63-
"password": "349d4728-438a-52a5-ad25-a740aa0bd240",
64-
"tenant": "891a9ddc-477a-4620-8f21-db22ffd3ffea"
65-
}
66-
```
67-
6845
## Create an ACS Kubernetes Cluster
6946

7047
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:
@@ -86,16 +63,14 @@ Execute the command to deploy the cluster. The `dns-prefix` and `ssh-key-value`
8663
```
8764
$ export SERVICE_NAME=myacs
8865
$ az acs create --resource-group="${RG_NAME}" --location="${DC_LOCATION}" \
89-
--service-principal="${SP_NAME}" \
90-
--client-secret="${SP_PASS}" \
9166
--orchestrator-type=kubernetes --master-count=1 --agent-count=2 \
9267
--agent-vm-size="Standard_D2_v2" \
9368
--admin-username="k8sadmin" \
9469
--name="${SERVICE_NAME}" --dns-prefix="mydnsprefix" \
9570
--ssh-key-value @/home/myusername/.ssh/id_rsa.pub
9671
```
9772

98-
> 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.
73+
> 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.
9974
10075
```
10176
{

0 commit comments

Comments
 (0)