Updated 10. Setting the solution up in AKS (Azure Kubernetes Service) (markdown)

Cesar De la Torre 2018-05-17 17:18:11 -07:00
parent 3dbe714f06
commit 0a5322a2dd

@ -215,12 +215,16 @@ Keep those credentials in a safe place.
Once the user and password are retrieved, run the following script for deployment. For example:
>```
>./deploy.ps1 -registry myregistry.azurecr.io -dockerUser User -dockerPassword SecretPassword -configFile file_with_config.yaml
>./deploy.ps1 -registry youreshopacrregistry.azurecr.io -dockerUser YoureShopAcrRegistry -dockerPassword YOUR-PASSWORD -configFile conf_local.yaml
>```
The parameter `configFile` is important (and mandatory) because it contains the configuration used for the Pods in Kubernetes. This allow deploying Pods that use your own resources in Azure or any other cloud provider. A configuration file `conf_local.yaml` is provided which configures Pods to use the infrastructure containers (that is sql server, rabbitmq, redis and mongodb must be deployed also in the k8s).
The parameter `configFile` is important (and mandatory) because it contains the configuration used for the Pods in Kubernetes. This allow deploying Pods that use your own resources in Azure or any other cloud provider.
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/ui](http://localhost:8001/ui)
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).
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/#!)
### Pods configuration file