This message was deleted.

Interestingly enough bouncing the hosts corrected the issue... Almost like nginx didn't let go of the port after it was replaced during the upgrade...

I had this on ALL of my hosts in two clusters just recently updated from 1.20 through to 1.23 (one ver at a time). All but one of the hosts was not passing traffic to the ingress.