-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nomad logs API/Command - general usage issues #3782
Comments
@jrasell This will be addressed in 0.8.0. If you would like to track this work, follow this branch: https://github.com/hashicorp/nomad/tree/f-tunnel. |
thanks @dadgar; looking forward to that. happy for you to close this if you want or keep open as a reference. |
Either way! I can close once the feature hits master. |
Is this still a planned feature? My nomad clients won't be accessible from my team's laptops, and only nomad server is available through a load balancer. It would be great if the nomad server could load the logs directly, then show them to me, rather than my browser trying to call the nomad client directly. |
@dcparker88 I believe this has made it into master at least so you can test locally potentially before any release candidate. |
thanks 👍 |
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. |
The Nomad logs command and API implementation/usage results in enforced connection to the Nomad node where the allocation resides as far as I am aware. In secure environments this poses a problem for the UI or any 3rd party tools that use server exposed APIs through a load balancer.
Is there any roadmap item for allowing the logs to be retired via the Nomad servers in something like a proxy behaviour?
Nomad version
Nomad 0.7.1
Reproduction steps
Navigate - https://demo.nomadproject.io/ui/allocations/d7c277c2-0883-bb72-3517-bd11618eafd6/mongo/logs
View the browser console and try to stream the logs and see an error such as:
Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR https://54.225.12.99:4646/v1/client/allocation/d7c277c2-0883-bb72-3517-bd11618eafd6/stats
The text was updated successfully, but these errors were encountered: