Nomad port-forward capability

[mr-karan]

Proposal

Similar to kubectl port-forward it would be nice to have a Nomad equivalent of the same. port-forward is sometimes helpful to test/debug your applications when it's not working the way you intended. It allows to access the service locally without exposing anywhere.

Use-cases

It's a niche use case, but there can be many for port-forward. My niche usecase was that I'd deployed a Prometheus instance on Nomad cluster which scrapes the targets from inside the cluster and sends the metric over the wire to a remote VictoriaMetrics cluster. This meant that I never really needed to expose Prometheus UI at all. Until, I needed to debug the config via UI :)

Attempted Solutions

At this point the only option is to SSH inside the nomad client node and use SSH tunneling to access it on my local machine. This is undesirable, since lot of devs won't have access to the host nodes and only cluster "admins" can do this.

Sidenote: I think implementing this would be similar to exec but curious to know more!

[jrasell]

Hi @mr-karan and thanks for raising this feature request.

We already have #6925 open which tracks the addition of a Nomad port-forward command and therefore I will close this issue out and use the linked one as the issue to track. If you could add any thumbs up and comments you might have to #6925 that would be appreciated.

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