UI: Ability to see task's logs even if client is not accessible from internet

[jacekjagiello]

Currently, web UI request task's logs using the IP address of a client, in which task is running on. But if a client is running in private subnet web UI tries to request it via private IP, which of course fails.
For example, if IP of a client in private network is 10.232.16.2, request for logs looks like this:

http://10.232.16.2.22:4646/v1/client/fs/logs/1fe767ac-...

Can we add some way to fetch logs from clients that are not accessible from internet? Maybe prepare endpoint in nomad server which proxies the request to a client? The same problem concerns other endpoints that communicate with nomad client, for example /v1/client/allocation/.../stats endpoint.

I'm happy to contribute, if we agree on some solution for this

[DingoEatingFuzz]

Hey @jacekjagiello, this is coming in 0.8 and is already in master!

• New server endpoints for proxying to clients: Client RPC Endpoints, Server Routing and Streaming RPCs #3892
• Changes to the UI to use the new endpoints, or falling back to them: UI: Take advantage of client request tunneling #3908

[jacekjagiello]

That's great news, can't wait for the next release!

[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.