There is Ingress, but traffic does not reach the pod. What could be the problem?

If Ingress is configured but traffic does not reach the pod, possible reasons include:

• Service selectors do not match pod labels. Ingress directs traffic to a service, and the service directs it to pods based on selectors. If the selector is incorrect, pods will not receive traffic.

• Endpoint issues. If the service has no Endpoints (no available pods), traffic will not be directed.

• NetworkPolicy issues. If network policies are set up in the cluster, they may block traffic to pods.

• Ingress Controller is not running or misconfigured. For example, the Ingress controller is absent or not started.

• Port or targetPort issues in the service. If targetPort does not match the port on which the application in the pod is listening.

• DNS or Ingress rules issues. Incorrect hosts or paths in the Ingress manifest.

To diagnose, check:

• kubectl get pods and kubectl describe pod — are the pods running?
• kubectl get svc and kubectl describe svc — is the service configured correctly?
• kubectl get endpoints — are there endpoints?
• Logs of the Ingress Controller.
• NetworkPolicy, if any.

Thus, the problem is most often related to incorrect service-pod linkage or Ingress Controller settings.