<p>my k8s master node has Public network IP, and worker node deploy in private net. worker node can connect to master but master cannot connect to worker node.</p>

<p>I have tested that can deploy a pod by kubectl, the pod running on worker node and master can watch pod status. but when I deploy a ingress, and access the ingress on master node, traffic cannot go to worker node.</p>

<p>I use flannel network.</p>

<p>I have tried use ssh tunnel, but it hard to management</p>

<p>I don't know if there are some suggests, thanks.</p>

<p>If you are deployed in a cloud environment, the most likely cause is incorrect firewall settings or route configurations. However, ingress configuration errors also may appear to look like infrastructure problems at times. </p>

<p>The Ingress will redirect your requests to the different services that it is registered with. The endpoint health is also monitored and requests will only be sent to active and healthy endpoints. My troubleshooting flow is as follows: </p>

<ol>
<li><p>Hit an unregistered path on your url and check if you get the default backend response. If no, then your ingress controller may not be correctly set up (whether it be domain name, access rules, or just configuration). If yes, then your ingress controller should be correctly set up, and this is a problem with the Ingress definition or backend.</p></li>
<li><p>Try hitting your registered path on your url. If you get a 504 gateway timeout, then your endpoint is accepting the request, but not responding correctly. You can follow the target pod logs to figure out whether it is behaving properly. </p></li>
</ol>

<p>If you get a 503 Service Unavailable, then your service might be down or deemed unhealthy by the ingress. In this case, you should definitely verify that your pods are running properly. </p>

<ol start="3">
<li>Check your nginx-ingress-controller logs to see how the requests are being redirected and what the internal responses are. </li>
</ol>
