From ff6819b0e11a1d3853b5b717c7ff44aef9ee8813 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Eduard=20Tom=C3=A0s?= Date: Fri, 11 Aug 2017 08:49:13 +0200 Subject: [PATCH] Updated 10. Setting the solution up in ACS Kubernetes (markdown) --- 10.-Setting-the-solution-up-in-ACS-Kubernetes.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/10.-Setting-the-solution-up-in-ACS-Kubernetes.md b/10.-Setting-the-solution-up-in-ACS-Kubernetes.md index 57cba3c..250e67b 100644 --- a/10.-Setting-the-solution-up-in-ACS-Kubernetes.md +++ b/10.-Setting-the-solution-up-in-ACS-Kubernetes.md @@ -193,6 +193,7 @@ Type the following in your command prompt: After logging in with a supported account identity, you can use either Azure Resource Manager mode or Azure Service Management mode CLI commands. 3. **Select your Azure subscription** You might have [several Azure subscriptions](https://docs.microsoft.com/en-us/cli/azure/account#set) as shown if you type the following. + >``` >az account list >``` @@ -262,13 +263,16 @@ Right after running that command you now will have the file `config` with the ne Or you an also verify connectivity to the ACS Kubernetes cluster by running `kubectl cluster-info`: - - * For further info about `az` tool and Kubernetes see the Azure Container Service [walkthrough](https://docs.microsoft.com/en-us/azure/container-service/container-service-kubernetes-walkthrough). * `az` is also helpful for getting the credentials `kubectl` needs to access your cluster. For other installation options, and information about configuring `kubectl` yourself, see the [Kubernetes documentation](https://kubernetes.io/docs/tasks/kubectl/install/). * For further info to connect to a Kubenetes cluster in ACS, see: [Connecting to a Kubernetes cluster in ACS](https://docs.microsoft.com/en-us/azure/container-service/container-service-connect) ## Deploying eShopOnContainers to Kubernetes in ACS (Azure Container Service) with the deployment script + +**Prerequisites** Before publishing the code to k8s you should have compiled and published your code to `obj/Docker/publish` folder (on any project path). The best way to do it is to run the `/cli-windows/buid-bits.ps1` script in windows or the `/cli-linux/build-bits-linux.sh` on Linux or the `/cli-mac/build-bits.sh` on Mac. + +If you prefer, you can force the `publish.ps1` script to build and publish the code for you using the `-buildBits $true` parameter. Using this parameter the publishing script will recompile and republish all projects (default value is `$false`). + We have simplified the deployment so you can do it just by executing a script by following the following few steps: 1. Open a PowerShell command line at the `k8s` directory of your local eShopOnContainers repository.