Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 6fd8cb1

Browse files
committedJun 11, 2020
Updated Readme doc
1 parent 6ef9962 commit 6fd8cb1

File tree

1 file changed

+14
-12
lines changed

1 file changed

+14
-12
lines changed
 

‎extensions/use-pod-identity-mid/README.md

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@ In this sub-project, you will work on completing the following tasks.
1010

1111
- Install *AAD Pod Identity* components on AKS cluster
1212
- Configure Azure SQL Database to allow *Managed Identity* access to resources (eg., Database Tables)
13-
- Deploy AAD Pod Identity application resoureces on AKS
14-
- Configure the Claims Web API application to retrieve data from Azure SQL Database Tables using Azure *Managed Identity*
13+
- Deploy AAD Pod Identity application resources on AKS
14+
- Deploy the Claims Web API application on AKS
1515

1616
**Functional Diagram:**
1717

@@ -158,10 +158,10 @@ To allow **Managed Identity** access to Azure SQL Database resources (eg., Table
158158

159159
![alt tag](./images/B-05.PNG)
160160

161-
## C. Deploy AAD Pod Identity resoureces on AKS
161+
## C. Deploy AAD Pod Identity resources on AKS
162162
**Approx. time to complete this section: 10 minutes**
163163

164-
1. Create a new Kubernetes namespace for deploying Claims Web API application;
164+
1. Create a new Kubernetes namespace for deploying Claims Web API application.
165165

166166
```bash
167167
# Create a new Kubernetes namespace 'dev-claims-mid' for deploying the Claims Web API application
@@ -204,10 +204,12 @@ To allow **Managed Identity** access to Azure SQL Database resources (eg., Table
204204
#
205205
```
206206

207-
## E. Deploy the Claims Web API application
208-
**Approx. time to complete this section: 20 minutes**
207+
## D. Deploy the Claims Web API application on AKS
208+
**Approx. time to complete this section: 30 minutes**
209+
210+
Login to the Linux VM (Bastion Host) via an SSH terminal window.
209211

210-
Login to the Linux VM (Bastion Host) via an SSH terminal window. Execute the steps below to deploy the Claims Web API application on AKS.
212+
Execute the steps below to deploy the Claims Web API application on AKS.
211213

212214
1. Modify the Claims Web API application configuration file.
213215

@@ -243,7 +245,7 @@ Login to the Linux VM (Bastion Host) via an SSH terminal window. Execute the st
243245

244246
3. Define and execute an Build Pipeline in Azure DevOps.
245247

246-
Login to [Azure DevOps Services](https://dev.azure.com/) and define a simple *Pipeline*. This pipeline should contain 2 tasks as detailed below.
248+
Login to [Azure DevOps Services](https://dev.azure.com/) and define a simple *Pipeline*. The pipeline should contain 2 tasks as detailed below.
247249

248250
- Docker **Build** Task: This task builds the Claims Web API application and application container image.
249251
- Docker **Push** Task: This task pushes the built application container image to ACR.
@@ -253,14 +255,14 @@ Login to the Linux VM (Bastion Host) via an SSH terminal window. Execute the st
253255

254256
Log back into the Linux VM.
255257

256-
Switch to the extensions directory `./extensions/use-pod-identity-mid`. Edit the Kubernetes application deployment manifest `./k8s-resources/deployment.yaml`. Update this file and specify correct values for attributes listed in the table below.
258+
Switch to this project extensions directory `./extensions/use-pod-identity-mid`. Edit the Kubernetes application deployment manifest `./k8s-resources/deployment.yaml`. Specify correct values for attributes listed in the table below.
257259

258260
| Attribute Name | Description |
259261
| -------------- | ----------- |
260262
acr-name | Name of the Azure Container Registry instance |
261-
tag-name | Azure DevOps Pipeline **Build ID**. Get the latest build ID from ACR. |
263+
tag-name | Azure DevOps Pipeline **Build ID**. Login to Azure Portal. Get the latest build ID from ACR **claims-api** repository. |
262264

263-
In case you have deployed an Ingress Controller (Nginx / Traefik) on the AKS cluster, you can also expose the API endpoint on the ingress controller by defining and deploying an *Ingress* resource (left as an exercise).
265+
In case you have deployed an Ingress Controller (Nginx / Traefik) on the AKS cluster, you can also expose the API endpoint on the ingress controller by deploying an *Ingress* resource (left as an exercise).
264266

265267
5. Create a new Kubernetes namespace for deploying Claims Web API with Managed Identity.
266268

@@ -296,4 +298,4 @@ Login to the Linux VM (Bastion Host) via an SSH terminal window. Execute the st
296298

297299
Access the Claims Web API service using a browser eg., http://[ALB Public IP]/api/v1/claims.
298300

299-
Congrats! In this extension, you installed **AAD Pod Identity** components on the AKS Cluster. You then configured the Claims Web API application to retrieve an OAuth token from Azure AD using **Managed Identity**. This token was used by the application to authenticate to Azure SQL Server. Finally, you deployed the application on AKS and verified the application is able to retrieve and send Claims documents to the SQL Database.
301+
Congrats! In this project extension, you installed **AAD Pod Identity** components on the AKS Cluster. You then configured the Claims Web API application to retrieve an OAuth token from Azure AD using **Managed Identity**. This token was used by the application to authenticate to Azure SQL Server. Finally, you deployed the application on AKS and verified the application is able to retrieve and send Claims documents to the SQL Database.

0 commit comments

Comments
 (0)
Please sign in to comment.