Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"502 bad gateway" error occurs on the login page after deploy the eshop to a Kubernetes cluster in Azure with AKS-Engine

See original GitHub issue

Reproduce Steps:

Deployed a Kubernetes cluster in Azure with AKS-Engine https://github.com/Azure/aks-engine/blob/master/docs/tutorials/quickstart.md#aks-engine-the-long-way 2)Setup Helm and Tiller $ kubectl apply -f helm-rbac.yaml $ helm init --history-max 200 --service-account tiller --node-selectors “beta.kubernetes.io/os=linux” 3)Create a static IP and set the dns az network public-ip create --resource-group eshop-aks-engine --name eshop-nginx-ingress-ip --sku Standard --allocation-method static --dns-name eshop-akse-cluster --query publicIp.ipAddress -o tsv 4)Create an ingress controller with a static public IP address in Azure Kubernetes Service $ helm install --name nginx-ingress --namespace ingress-nginx –set controller.nodeSelector.“beta.kubernetes.io/os”=linux --set defaultBackend.nodeSelector."beta\.kubernetes\.io\/os"=linux –set controller.service.loadBalancerIP=“52.139.175.102” --set controller.service.annotations."service\.beta\.kubernetes\.io/azure-dns-label-name"="eshop-akse-cluster" –set rbac.create=true ` stable/nginx-ingress 5)Install eShopOnContainers using Helm .\deploy-all-aks.ps1 -externalDns eshop-akse-cluster.eastasia.cloudapp.azure.com -aksName eshopaksenginetestcluster -aksRg eshop-aks-engine -imageTag linux-dev -useMesh $false Note: Changed the “ingressValuesFile” to “ingress_values_dockerk8s.yaml” in the deploy-all-aks.ps1 file. 6)View the services
click “LOGIN” on the http://eshop-akse-cluster.eastasia.cloudapp.azure.com/webmvc page
Enter the User name and Password on the login page and click “[LOG IN]”