From 73880f2b973c5340b726e2a67ecc7830ff4e5de1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Eduard=20Tom=C3=A0s?= Date: Fri, 21 Sep 2018 13:03:31 +0200 Subject: [PATCH] Updated 10.1 Deploying to Kubernetes (AKS and local) using Helm Charts (markdown) --- ...bernetes-(AKS-and-local)-using-Helm-Charts.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/10.1-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts.md b/10.1-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts.md index 6fe99e1..07bc36c 100644 --- a/10.1-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts.md +++ b/10.1-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts.md @@ -139,7 +139,21 @@ eshop-webstatus eshop...aksapp.io 80 Ingresses are automatically configured to use the public DNS of the AKS provided by the "https routing" addon. -You can view the MVC client at http:///webmvc and the SPA at the http:/// +One step more is needed: we need to configure the nginx ingress controller that AKS has to allow more large headers. This is because the headers sent by identity server exceed the size configured by default. Fortunately this is very easy to do. Just type (from the `/k8s/helm` folder): + +``` +kubectl apply -f aks-httpaddon-cfg.yaml +``` + +Then you can restart the pod that runs the nginx controller. Its name is `addon-http-application-routing-nginx-ingress-controller-` and runs on `kube-system` namespace. So run a `kubectl get pods -n kube-system` find it and delete with `kubectl delete pod -n kube-system`. + +**Note:** If running in a bash shell you can type: + +``` +kubectl delete pod $(kubectl get pod -l app=addon-http-application-routing-nginx-ingress -n kube-system -o jsonpath="{.items[0].metadata.name}) -n kube-system +``` + +You can view the MVC client at http://[dns]/webmvc and the SPA at the http://[dns]/ ## Customizing the deployment