mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-29 06:29:34 +00:00
Update _index.md
Added information about adding the Azure SP and SP Role needed for creating a Rancher Node Template
This commit is contained in:
@@ -20,6 +20,16 @@ Use {{< product >}} to create a Kubernetes cluster in Azure.
|
|||||||
|
|
||||||
6. {{< step_create-cluster_node-pools >}}
|
6. {{< step_create-cluster_node-pools >}}
|
||||||
|
|
||||||
|
Before creating a **node template** in Rancher using a cloud infrastructure such as Azure, we must configure Rancher to allow the manipulation of resources in an Azure subscription.
|
||||||
|
|
||||||
|
To do this, we will first create a new Azure **service principal (SP)** in Azure **Active Directory (AD)**, which, in Azure, is an application user who has permission to manage Azure resources.
|
||||||
|
|
||||||
|
The following is a template `az cli` script that you have to run for creating an service principal, where you have to enter your SP name, role, and scope:
|
||||||
|
|
||||||
|
`az ad sp create-for-rbac --name="<Rancher ServicePrincipal name>" -- role="Contributor" --scopes="/subscriptions/<subscription Id>"`
|
||||||
|
|
||||||
|
The creation of this service principal returns three pieces of identification information, *The application ID, also called the client ID*, *The client secret*, and *The tenant ID*. This information will be used in the following section adding the **node template**.
|
||||||
|
|
||||||
1. Click **Add Node Template**.
|
1. Click **Add Node Template**.
|
||||||
|
|
||||||
2. Complete the **Azure Options** form.
|
2. Complete the **Azure Options** form.
|
||||||
|
|||||||
Reference in New Issue
Block a user