ayan.poddar/eShopOnContainers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated 10. Setting the solution up in AKS (Azure Kubernetes Service) (markdown)

Cesar De la Torre 2018-05-17 15:08:50 -07:00
parent bd3c32794e
commit 8ecf3f00ab
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
10.-Setting-the-solution-up-in-AKS-(Azure-Kubernetes-Service).md

@ -46,12 +46,12 @@ All previous steps related to Azure infrastructure can be skipped if you run the
For example just by running the following cli script it would create to create the AKS cluster.
>```
>./gen-k8s-env-aks -resourceGroupName k8sGroup -location westeurope -registryName k8sregistry -dnsName k8s-dns -serviceName k8s-cluster -createAcr true -nodeCount 3 -nodeVMSize Standard_D2_v2
>./gen-k8s-env-aks -resourceGroupName YoureShopAksResgroup -location centralus -serviceName YoureShopAksCluster -dnsNamePrefix youreshopaks -registryName YoureShopAcrRegistry -createAcr true -nodeCount 3 -nodeVMSize Standard_D2_v2
>```
**Important**: Note the parameter "-createAcr true". If you are creating the K8s cluster but you want to re-use and existing ACR, say "-createAcr false".
### Step-by-step
### Step-by-step procedure
* Authenticate in Azure using the CLI
Before running the eShopOnContainers **gen-k8s-env-aks.ps1** script or manually creating the clusters, you first need to authenticate from a PowerShell window, with:
@ -77,8 +77,12 @@ Open PowerShell and position in the folder where the script is placed:
Run the following script:
>```
>./gen-k8s-env-aks -resourceGroupName k8sGroup -location westeurope -registryName k8sregistry -dnsName k8s-dns -serviceName k8s-cluster -createAcr true -nodeCount 3 -nodeVMSize Standard_D2_v2
>./gen-k8s-env-aks -resourceGroupName YoureShopAksResgroup -location centralus -serviceName YoureShopAksCluster -dnsNamePrefix youreshopaks -registryName YoureShopAcrRegistry -createAcr true -nodeCount 3 -nodeVMSize Standard_D2_v2
>```
You should get a similar execution in PowerShell, as the following: