Nginx: 502 Bad Gateway error after deploying redmine in kubernetes cluster

6/30/2019

I tried to deploy redmine in kubernetes cluster (containing 1 master and 2 workers) through this helm chart "https://gitlab.com/kanzari.1993/redmine" with nginx ingress controller enabled, the deployment done with success but when I tried to access the application through the name of the host mentioned in the ingress.yaml file I get this warning: "502 Bad Gateway nginx / 1.17.0" on the other hand all the pods are in "running" state.

Do you have an idea about how to solve this problem?

I think the problem is coming from the deployed application itself "redmine" there is the outputs to explain more the situation. Capture1Capture2Capture3Capture4

-- Mehrez Kanzari
docker
kubernetes
kubernetes-helm
kubernetes-ingress
redmine

1 Answer

7/1/2019

Can you check how much time kube-proxy take to resolve service to pod IPs? Check this on the node running nginx POD. Sometimes under load, kube-proxy can take more time than expected and result in 502.

-- Akash Sharma
Source: StackOverflow