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-18 13:03:51 -07:00
parent 24766a5712
commit 9691e223d0
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -256,7 +256,7 @@ The parameter `configFile` is important (and mandatory) because it contains the
If the configuration file name you provide is `conf_local.yaml`, in addition to the application containers, it will deploy the infrastructure containers (that is, SQL Server container, RabbitMQ container, Redis container and MongoDB container will also be deployed into the Kubernetes cluster). If the configuration file name you provide is `conf_local.yaml`, in addition to the application containers, it will deploy the infrastructure containers (that is, SQL Server container, RabbitMQ container, Redis container and MongoDB container will also be deployed into the Kubernetes cluster).
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). This file is, however, provided just as a reference file because it doesn't have valid values for Azure resources. You'd need to provide your Azure configuration if you want to use infrastructure resources which are external to the Kubernetes cluster. If the configuration file name you provide is `conf_cloud.yaml` 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). This file is, however, provided just as a reference file because it doesn't have valid values for Azure resources. You'd need to provide your Azure configuration if you want to use infrastructure resources which are external to the Kubernetes cluster.
The execution will start like the following: The execution will start like the following:
@ -294,22 +294,22 @@ The script accepts the following parameters:
### Typical usages of the script: ### Typical usages of the script:
* Build all the images, push the images in a organization called `foo` in DOCKER HUB (instead of ACR). Images will be tagged with my current git branch and containers will use the configuration set in `conf_local.yml` file when deployed all the containers in Kuberentes, including infrastructure containers: * Build all the images, push the images in a organization called `foo` in DOCKER HUB (instead of ACR). Images will be tagged with my current git branch and containers will use the configuration set in `conf_local.yaml` file when deployed all the containers in Kuberentes, including infrastructure containers:
``` ```
./deploy.ps1 -buildImages $true -dockerOrg foo -dockerUser MY_USER -dockerPassword MY_PASSWORD -configFile conf_local.yml ./deploy.ps1 -buildImages $true -pushImages $true -dockerOrg foo -dockerUser MY_USER -dockerPassword MY_PASSWORD -configFile conf_local.yaml
``` ```
* Do not build Docker images. Create Kubernetes deployments that will pull images from my private repository such as in ACR registry, in the `foo` organization, using the tag `latest`. Containers will use the configuration set in `conf_cloud.yml` file. * Do not build Docker images, neither push it to the registry. Then, create Kubernetes deployments that will pull images from my private repository such as in ACR registry, in the `foo` organization, using the tag `latest`. Containers will use the configuration set in `conf_cloud.yaml` file.
``` ```
./deploy.ps1 -buildImages $false -dockerOrg foo -registry MY_REGISTRY_FQDN -dockerUser MY_USER -dockerPassword MY_PASSWORD -configFile conf_cloud.yml -imageTag latest ./deploy.ps1 -buildImages $false -pushImages $false -dockerOrg foo -registry MY_REGISTRY_FQDN -dockerUser MY_USER -dockerPassword MY_PASSWORD -configFile conf_cloud.yaml -imageTag latest
``` ```
* Deploy all containers (including infrastructure containers) into Kuberentes using the public eShopOnContainers images that Microsoft provides at Docker Hub, using the tag `dev`: * Deploy all containers (including infrastructure containers) into Kuberentes using the public eShopOnContainers images that Microsoft provides at Docker Hub, using the tag `dev`:
``` ```
./deploy.ps1 -buildImages $false -configFile conf_local.yml -imageTag dev ./deploy.ps1 -buildImages $false -pushImages $false -configFile conf_local.yaml -imageTag dev
``` ```