Skip to content

Commit c9ccd7c

Browse files
committed
Updated Readme doc
1 parent 71d62e4 commit c9ccd7c

File tree

1 file changed

+16
-5
lines changed

1 file changed

+16
-5
lines changed

README.md

Lines changed: 16 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -486,7 +486,19 @@ Before proceeding, login into the Linux VM using SSH.
486486
$ pwd
487487
/home/labuser/git-repos/aks-aspnet-sqldb-rest
488488
#
489-
# Run the docker build. The build will take a few minutes to download both the .NET core build and run-time containers!
489+
# Run the docker build.
490+
# The build will take a few minutes to download both the .NET core build and run-time
491+
# containers!
492+
# NOTE:
493+
# The 'docker build' command does the following (Review the 'dockerfile'):
494+
# 1. Build the dotnet application
495+
# 2. Layer the application binaries on top of a base container image
496+
# 3. Create a new application container image
497+
# 4. Save the built container image on the host (local machine)
498+
#
499+
# DO NOT forget the dot '.' at the end of the 'docker build' command !!!!
500+
# The '.' is used to set the context directory (path to the dockerfile) for the docker build.
501+
#
490502
$ docker build -t claims-api .
491503
#
492504
# List the docker images on this VM. You should see two container images -
@@ -746,7 +758,6 @@ Before proceeding with the next steps, take a few minutes and go thru the **dock
746758
- Azure Subscription = Select your Azure Subscription.
747759
- Azure Container Registry = Select ACR which you provisioned in [Section E](#e-deploy-azure-container-registry) above.
748760
- Action = `Push an image`
749-
- Docker File = `dockerfile`
750761
- Image Name = `claims-api:$(Build.BuildId)`
751762
- Qualify Image Name = Enable checkbox.
752763
- Include Latest Tag = Enable checkbox.
@@ -820,9 +831,9 @@ Follow the steps below to provision the AKS cluster and deploy the Claims API mi
820831
821832
3. Provision an AKS cluster.
822833
823-
>**NOTE:** Follow the steps in one of the options below (a. or b.) for deploying the AKS cluster. If you would like to explore deploying containers on **Virtual Nodes** in the [extensions](./extensions) projects, follow the steps in option (b) below. Otherwise, follow the steps in option (a).
834+
>**NOTE:** Follow the steps in one of the options **A** or **B** below for deploying the AKS cluster. If you would like to explore deploying containers on **Virtual Nodes** in the [extensions](./extensions) projects, follow the steps in option **B** below. Otherwise, follow the steps in option **A**.
824835
825-
a. Use the latest supported Kubernetes version to deploy the AKS cluster. At the time of this writing, version `1.11.5` was the latest AKS version.
836+
**A.** Use the latest supported Kubernetes version to deploy the AKS cluster. At the time of this writing, version `1.11.5` was the latest AKS version.
826837
827838
Refer to the commands below to create the AKS cluster. It will take a few minutes (< 10 mins) for the AKS cluster to get provisioned.
828839
```bash
@@ -839,7 +850,7 @@ Follow the steps below to provision the AKS cluster and deploy the Claims API mi
839850
# Verify status of AKS cluster
840851
$ az aks show -g myResourceGroup -n akscluster --output table
841852
```
842-
b. With this option, the AKS cluster will be provisioned in a private virtual network on Azure. You will need **Owner** level permission (role) for the Azure Subscription in order to proceed with the next steps.
853+
**B.** With this option, the AKS cluster will be provisioned in a private virtual network on Azure. You will need **Owner** level permission (role) for the Azure Subscription in order to proceed with the next steps.
843854
844855
```bash
845856
# Create a virtual network

0 commit comments

Comments
 (0)