This message was deleted.

1. Most likely the configuration of Ingress Kubernetes resource is not correct. One of ways to troubleshoot this is to think of NGINX Ingress as normal NGINX: so you can connect to one of PODs and check which configuration is generated based on Ingress(es) that you have (eg. nginx -T command) and you will have some logs there as well (well, to STDOUT, so kubectl logs) 2. Probably this is via configuration of default backend as explained in https://loft.sh/blog/kubernetes-nginx-ingress-10-useful-configuration-options/#default-backend?utm_medium=reader&utm_source=loft-blog&utm_campaign=blog_kubernetes-nginx-ingress-10-useful-configuration-options and then using https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#denylist-source-range annotation on it that contains some wildcard like * to cover all IPs