Skip to content

Commit e8dbff8

Browse files
committed
fix last request
1 parent 1de8f19 commit e8dbff8

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

articles/openshift/howto-create-service-principal.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,26 @@ The following sections explain how to use the Azure portal to create a service p
104104

105105
## Create a service principal - Azure portal
106106

107+
To create a service principal using the Azure portal, complete the following steps.
107108

109+
1. On the Create Azure Red Hat OpenShift **Basics** tab, create a resource group for your subscription, as shown in the following example.
110+
111+
:::image type="content" source="./media/basics-openshift-sp.png" alt-text="Screenshot that shows how to use the Azure Red Hat service principal with Azure portal to create a cluster." lightbox="./media/basics-openshift-sp.png":::
112+
113+
2. Click **Next: Authentication** to configure and deploy the service principal on the **Authentication** page of the **Azure Red Hat OpenShift** dialog.
114+
115+
:::image type="content" source="./media/openshift-service-principal-portal.png" alt-text="Screenshot that shows how to use the Azure Red Hat service principal with Azure portal to create a cluster." lightbox="./media/openshift-service-principal-portal.png":::
116+
117+
In the **Service principal information** section:
118+
119+
- **Service principal client ID** is your appId.
120+
- **Service principal client secret** is the service principal's decrypted Secret value.
121+
122+
In the **Cluster pull secret** section:
123+
124+
- **Pull secret** is your cluster's pull secret's decrypted value. If you don't have a pull secret, leave this field blank.
125+
126+
After completing this tab, select **Next: Networking** to continue creating your cluster. Select **Review + Create** when you complete the remaining tabs.
108127

109128
> [!NOTE]
110129
> This service principal only allows a contributor over the resource group the Azure Red Hat OpenShift cluster is located in. If your VNet is in another resource group, you need to assign the service principal contributor role to that resource group as well.

0 commit comments

Comments
 (0)