From dbb63b6817d4536ea1dddddc014d416836de156f Mon Sep 17 00:00:00 2001 From: Steve Smith Date: Mon, 26 Aug 2019 06:48:43 -0400 Subject: [PATCH 1/3] fixed typo --- Architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Architecture.md b/Architecture.md index 8325de8..e7c63ce 100644 --- a/Architecture.md +++ b/Architecture.md @@ -18,7 +18,7 @@ For a production-grade solutions you should use a more robust implementation bas The architecture also includes an implementation of the API Gateway pattern and Backend-For-Front-End (BFF), to publish simplified APIs and include additional security measures for hiding/securing the internal microservices from the client apps or outside consumers. -These sample API Gateways based on [Ocelot](https://github.com/ThreeMammals/Ocelot), an OSS lightweight API Gateway solution. The API Gateways are deployed as autonomous microservices/containers, so you can test them in a simple development environment by just using Docker Desktop or even with orchestrators like Kubernetes in AKS or Service Fabric. +These sample API Gateways are based on [Ocelot](https://github.com/ThreeMammals/Ocelot), an OSS lightweight API Gateway solution. The API Gateways are deployed as autonomous microservices/containers, so you can test them in a simple development environment by just using Docker Desktop or even with orchestrators like Kubernetes in AKS or Service Fabric. For a production-ready architecture you can either keep using Ocelot, which is simple and easy to use, and it's currently used in production by large companies. If you need additional functionality and a much richer set of features suitable for commercial APIs, you can also substitute those API Gateways and use Azure API Management or any other commercial API Gateway, as shown in the following diagram. From b55e4ea44e50e7c2a36354c8daf32ae34ca0a111 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Eduard=20Tom=C3=A0s?= Date: Tue, 10 Sep 2019 17:23:29 +0200 Subject: [PATCH 2/3] Updated Deploy to Local Kubernetes (markdown) --- Deploy-to-Local-Kubernetes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Deploy-to-Local-Kubernetes.md b/Deploy-to-Local-Kubernetes.md index d8ba023..5d3a51b 100644 --- a/Deploy-to-Local-Kubernetes.md +++ b/Deploy-to-Local-Kubernetes.md @@ -120,7 +120,7 @@ Then, just run this script from the `k8s\helm` folder, to deploy your local imag The parameter `useLocalk8s` to `$true`, forces the script to use `localhost` as the DNS for all Helm charts and also creates the ingress with the correct ingress class. -When using the parameter `useLocalImages` to `$true`, helm tries to use the local images first, and if not available locally, pulls the official ones from DockerHub. +**Note**: When using the parameter `imagePullPolicy` to `Never` only local images will be used (_pods_ will enter in error state if local images do not exist. If `imagePullPolicy` is set to `IfNotPresent` then local images will be used if present, and if not Kubernetes will try to download them from a docker registry. If the `imagePullPolicy` is set to `Always` then Kubernetes will never use the local images and will try to download them all from a docker registry. If the images are not found _pods_ will enter in error state. ### Deploy the public official eShopOnContainer images from DockerHub From 479ffb7f0e2556e0cbfba3b6563d0dfd6e426284 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Eduard=20Tom=C3=A0s?= Date: Tue, 10 Sep 2019 17:23:52 +0200 Subject: [PATCH 3/3] Updated Deploy to Local Kubernetes (markdown) --- Deploy-to-Local-Kubernetes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Deploy-to-Local-Kubernetes.md b/Deploy-to-Local-Kubernetes.md index 5d3a51b..34056c9 100644 --- a/Deploy-to-Local-Kubernetes.md +++ b/Deploy-to-Local-Kubernetes.md @@ -115,7 +115,7 @@ docker-compose build Then, just run this script from the `k8s\helm` folder, to deploy your local images: ```powershell -.\deploy-all.ps1 -imageTag linux-latest -useLocalk8s $true -useLocalImages $true +.\deploy-all.ps1 -imageTag linux-latest -useLocalk8s $true -imagePullPolicy Never ``` The parameter `useLocalk8s` to `$true`, forces the script to use `localhost` as the DNS for all Helm charts and also creates the ingress with the correct ingress class.