502 Bad Gateway errors from Kubernetes Ingress When Blazor Server apps build on .NET 8 GA image

After migrating our test images to build with .NET GA images this week, my Kubernetes ingress has started returning 502 bad gateways when services running behind it are on this image.

I've been testing using .NET 8 docker images since RC1 with no issue after accounting for the documented port changes. The only change made is I now build using the GA images. The docker files remained unchanged as they are using the 8.0 tag, all that happened it time passed and the 8.0 tagged images were updated at source.

The services are very much alive in the environment, they just aren't responding to calls that they were happy to speak to using RC1 and RC2. Has anything changed in this regard between RC2 and GA?

The services I'm running are Blazor Server websites which rely on signal R connections, although I don't know of the relevance of this, it appears the connection fails in ingress. I see this in my ingress logs:

(connect() failed (111: Connection refused) while connecting to upstream, client:).

I don't think I'm alone here, as [this issue raised on stack overflow seems similar](https://stackoverflow.com/questions/77536194/signalr-on-docker-container-bad-gateway-after-upgrading-to-net8)

Thanks,
Carl