Updated 10. Setting the solution up in ACS Kubernetes (markdown)

10.-Setting-the-solution-up-in-ACS-Kubernetes.md

@@ -292,7 +292,10 @@ We have simplified the deployment so you can do it just by executing a script by
 >```
 <img src="img/kubernetes/acr-passwords.png">
 
-Once the user and password are retrieved, run the following script for deployment, including your values and password. For example:
+Once the credentials are retrieved to your local machine you can now run any Kubernetes CLI command, like when using KUBECTL.
+Therefore, you can now deploy the application by executing the following eShopOnContainers deployment to K8s script, 
+
+The following example uses your already available Azure Container Registry where the script will push the Docker images  created as part of the process.
 >```
 >./deploy.ps1 -registry eshopautogencontainerregistry.azurecr.io -dockerUser eShopAutogenContainerRegistry -dockerPassword YourSuperSecretPassword -configFile ./conf_local.yml
 >```
@@ -303,6 +306,14 @@ 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:
 <img src="img/kubernetes/azure-container-service-repos.png">
 
+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.
+
+>```
+>.\deploy.ps1 -configFile .\conf_local.yml -buildImages $false -imageTag dev
+>```
+
+Note that in this last case it just needs the config for the services/containers to deploy because we're explicitely saying we don't want to build the Docker Images, neither pushing the images to any specific Docker Registry (like ACR), so it will just use the available images at Docker Hub for the deployment.
+
 You can also watch the deployment unfold from the Kubernetes web interface by running `kubectl proxy` in a different PowerShell or bash window and open a browser to [http://localhost:8001/ui](http://localhost:8001/ui) as in the following screenshot:
 
 <img src="img/kubernetes/kubernetes-admin-ui-01.png">