With all services deployed to the same namespace now, ingress-nginx now has policies applied to it which results in anything not defined being blocked, the load balancer being the issue
This change adds the allow-external label to the nginx ingress which allows all traffic to the ingress pod, which was previously the default as ingress-nginx was deployed in it's own namespace with no network policies
viv-4
commented
1 year ago
With all services deployed to the same namespace now, ingress-nginx now has policies applied to it which results in anything not defined being blocked, the load balancer being the issue This change adds the
allow-externallabel to the nginx ingress which allows all traffic to the ingress pod, which was previously the default as ingress-nginx was deployed in it's own namespace with no network policies