How to Access Aspire Dashboard via Kubernetes Ingress When Running in AppHost?

[fortunes-guardian]

Hi team,

I’ve successfully accessed the Aspire dashboard in a few scenarios:

Locally: e.g., https://localhost:17289
Standalone Docker image:
This works as expected and the dashboard listens on all interfaces (http://[::]:18888).

My challenge:
I am now trying to access the dashboard when running inside a container in Kubernetes (using the AppHost, not the standalone dashboard image).

The app is launched in a CI/CD build step with: dotnet run

so it should be using launchSettings.json.

The container exposes port 17289.

I have set up a Kubernetes service and ingress to route traffic to this port on the agent pod.

Problem:
Despite this setup, I cannot access the dashboard externally.
From what I can see, the dashboard in the AppHost model is only listening on the loopback interface (127.0.0.1/localhost) inside the container, not on 0.0.0.0 or [::].

This means Kubernetes cannot route traffic from outside the container to the dashboard.

In contrast, the standalone dashboard image outputs:
info: Aspire.Dashboard.DashboardWebApplication[0] Now listening on: http://[::]:18888

Question:
How can I configure the Aspire dashboard (when running as part of the AppHost) to listen on all interfaces (0.0.0.0 or [::]) so that it is accessible via Kubernetes ingress?
Is there a recommended way to achieve this, or a setting I’m missing in launchSettings.json or via environment variables?

It would be excellent to be able to access the dashboard in the AppHost scenario for debugging and monitoring in CI/CD and Kubernetes environments.

Thank you for your help!

[danegsta]

This should be fixed in #9977 which will ship as part of 9.4; the AppHost was previously only binding services to localhost, regardless of the specific service or endpoint configuration.

[fortunes-guardian]

Thanks very much @danegsta, looking forward to it.