Nomad UI requires direct client access

[holtwilkins]

Nomad version

0.7.0

Issue

The Nomad web UI, when attempting to view a particular client as in the ui/nodes/<node ID> UI endpoint, attempts to reach-out to that client directly on port 4646.

Expected Behavior

Although running the Nomad CLI also attempts to reach-out directly to nodes, I would expect that the server (via the UI) would be intended to be treated as a proxy, so to speak, for accessing information like this on clients. I.e. I would expect that direct access to all Nomad client API endpoints from all human clients shouldn't be a requirement from a network perspective.

[dadgar]

For the time being this is as designed. It is using the same API's as the CLI so the experience will be the same for both of them. This may change in the future.

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.