From f18e73903d24fb067e286912f928eeba68aa0767 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Thu, 17 May 2018 17:42:49 -0700 Subject: [PATCH] Updated 10. Setting the solution up in AKS (Azure Kubernetes Service) (markdown) --- ...ution-up-in-AKS-(Azure-Kubernetes-Service).md | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/10.-Setting-the-solution-up-in-AKS-(Azure-Kubernetes-Service).md b/10.-Setting-the-solution-up-in-AKS-(Azure-Kubernetes-Service).md index d091d7a..724a445 100644 --- a/10.-Setting-the-solution-up-in-AKS-(Azure-Kubernetes-Service).md +++ b/10.-Setting-the-solution-up-in-AKS-(Azure-Kubernetes-Service).md @@ -222,7 +222,11 @@ Run second script for ingress (it has several patches related to Azure): **IMPORTANT** - You need to wait for a while until the ingress tiers are created before trying to deploy the application containers. Other than that you will still get the error "Must install ingress first - Run deploy-ingress.ps1 and deploy-ingress-azure.ps1". -1. Finally, in order to deploy the application containers, run `deploy.ps1` with your ACR registry information. The Docker username and password are provided by Azure Container Registry, and can be retrieved from the Azure portal. Optionally, ACR credentials can be obtained by running the following command: +Errors if ingresses are still not available: +![image](https://user-images.githubusercontent.com/1712635/40210277-df007906-59f8-11e8-88c6-a6044eb61844.png) + +**Deploy eShopOnContainers into Kuberentes:** +Finally, in order to deploy the application's containers, run `deploy.ps1` with your ACR registry information. The Docker username and password are provided by Azure Container Registry, and can be retrieved from the Azure portal. Optionally, ACR credentials can be obtained by running the following command: >``` >az acr credential show -n eshopregistry @@ -240,7 +244,15 @@ If the configuration file name you provide is `conf_local.yaml`, in addition to If the configuration file name you provide is `conf_cloud.yml` it will just deploy the application containers. All the infrastructure should be deployed as Azure PaaS services such as Azure SQL Database, Azure Redis, Azure CosmosDB and Azure Service Bus instead of the dev/test infrastructure containers). -The script will build the code and corresponding Docker images, push the later to your registry, and deploy the application to your cluster. You can watch the deployment unfold from the Kubernetes web interface: run `kubectl proxy` and open a browser to [http://localhost:8001/#!](http://localhost:8001/#!) +The execution will start like the following: + +![image](https://user-images.githubusercontent.com/1712635/40210357-4e8f39c4-59f9-11e8-857c-981dfd823a33.png) + +The script will build the .NET code (microservices and ASP.NET web apps) and build their corresponding Docker images, push the later to your ACR registry, and deploy the containers from ACR into your Kubernetes cluster. + +You can watch the deployment unfold from the Kubernetes web interface: +run `kubectl proxy` and open a browser to [localhost:8001/#!/deployment](localhost:8001/#!/deployment) + ### Pods configuration file