Dagster Webserver erroneously shows Code Locations in a Loading... state with multiple replicas after upgrading to v1.11

What's the issue?

Exactly the same as described in my previous issue related to dagster v1.8: https://github.com/dagster-io/dagster/issues/23753

Now we upgraded to Dagster v1.11.x from v1.10.x. We've currently tested with v1.11.5 and the latest version v1.11.10. Both v1.11 version have the issue described in my previous issue again.

Some screenshots from /locations in dagster v.1.11.x

What did you expect to happen?

The /locations page works the same in Dagster < v1.11 as in v1.11.

How to reproduce?

Deploy the Dagster helm chart (1.11.5 or 1.11.10) to a Kubernetes cluster with at least 2 replica's for the webserver enabled behind a load balancer. In our case Traefik.

Dagster version

1.11.10

Deployment type

Dagster Helm chart

Deployment details

Dagster helm v1.11.10 with multiple replica's enabled for the webserver behind a Traefik ingress.

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a ! We factor engagement into prioritization.