ayan.poddar/eShopOnContainers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated 10.1 Deploying to Kubernetes (AKS and local) using Helm Charts (markdown)

Eduard Tomàs 2018-09-21 13:03:31 +02:00
parent aaae095995
commit 73880f2b97
1 changed files with 15 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
10.1-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts.md

@ -139,7 +139,21 @@ eshop-webstatus eshop.<your-guid>.<region>.aksapp.io <public-ip> 80
Ingresses are automatically configured to use the public DNS of the AKS provided by the "https routing" addon. 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://<dns>/webmvc and the SPA at the http://<dns>/ 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-<something>` and runs on `kube-system` namespace. So run a `kubectl get pods -n kube-system` find it and delete with `kubectl delete pod <pod-name> -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 ## Customizing the deployment