From bb55182bdc4e49aa53a5ee6fce07d3eb2f903e7d Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Thu, 21 Sep 2017 10:34:41 -0700 Subject: [PATCH] Updated 10. Setting the solution up in ACS Kubernetes (markdown) --- 10.-Setting-the-solution-up-in-ACS-Kubernetes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/10.-Setting-the-solution-up-in-ACS-Kubernetes.md b/10.-Setting-the-solution-up-in-ACS-Kubernetes.md index 16c61f8..9eb9979 100644 --- a/10.-Setting-the-solution-up-in-ACS-Kubernetes.md +++ b/10.-Setting-the-solution-up-in-ACS-Kubernetes.md @@ -306,7 +306,7 @@ The script will build the .NET Core code, SPA TypeScript code and corresponding While deploying eShopOnContainers with the script, you can see the Docker image repositories being created in your **Azure Container Registry** which happens right before deploying to Kubernetes, at the Azure's portal: -Another deployment example would be to "NOT create the Docker images" and "NOT to use your Azure Container Registry" but instead just deploy the already available eShopOncontainer images already available at Docker Hub (Public Docker Registry). In this case, it won't be using your code but the Docker images created by us, though. +Another deployment example would be to "do NOT build the Docker images" and to "do NOT use your Azure Container Registry" but instead just deploy the eShopOncontainer images already available at Docker Hub (Public Docker Registry). In this case, it won't be using your code but the Docker images built and pushed by us to Docker Hub, though. >``` >.\deploy.ps1 -configFile .\conf_local.yml -buildImages $false -imageTag dev