-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NGINX Ingress can't access service ClusterIP (502 bad gateway error) #6110
Comments
means the ingress controller pod cannot reach the node where fabsgoblog svc is running. |
The logs:
means that nginx is accessing at application since the endpoint This socket, is the endpoint of you service. You can see it, do it:
In this case, is the endpoints of service For test it, entry in the pod of ingress controller and checks the connection.
As we see exactly , this cannot access. You look that IP has the service
And as we see, the pod has access. With the ClusterIP and Port of the service. So that a solution would be do the follow. You must tell at Ingress, that uses the ClusterIP:port instead of use endpoints list of ingress controller. For this you edit the Ingress resource and add the follow
FYI Service Upstream¶By default the Ingress-Nginx Controller uses a list of all endpoints (Pod IP/port) in the NGINX upstream configuration. The This can be desirable for things like zero-downtime deployments . See issue #257. Known Issues¶If the
|
add this annotation , still have this problem, same issue msg, |
Hi! After successfully deployed application (pod looks OK, logs are ok), I created ClusterIP service, then created NGINX Ingress. When I try to access NGINX NodePort, I get 502 bad gateway error. Checking NGINX logs, it can't access the ClusterIP and port.
Details:
NGINX Ingress version
** Kubernetes version**
Service
Ingress
GET SERVICE
ERROR
LOGS
Please help,
Cheers!!!
The text was updated successfully, but these errors were encountered: