-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feature : Support Nomad Task API #3
Comments
@henrikjohansen My PR #4 should provide support for what you requested. I haven't tested it on a cluster yet, but maybe you can build the docker file and test it? |
Upgrade nomad api package to support unix domain sockets. Fixes #3
you could try this build from main branch ghcr.io/ituoga/coredns-nomad:main |
@blinkinglight Something seems off, running the above image I get unsupported protocol scheme "unix" ...
The corresponding Corefile is :
|
@henrikjohansen Could you try without |
So I just tried this locally via a manually built coredns and it did work, I wonder if something is wonky with the build process so that it fetched the wrong nomad api client? |
#5 has a working readme for the task api. I also fixed the Dockerfile so you can easily build this locally and test (till @blinkinglight merged it). I just verified it on a test machine. |
api.sock requires token . |
You shouldn't need to specify the token if you use the task file I have added to the readme (it passes the token as env var)
…On Sun, Dec 1, 2024, at 17:15, M wrote:
api.sock requires token .
token [token]
address unix:///secrets/api.sock
and it works.
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAT5C5Q7A5XRD6DKKA5UYD2DMY25AVCNFSM6AAAAABIZMBC4CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBZHEYTGMZQHE>.
You are receiving this because you commented.Message ID:
***@***.***>
|
that works too. thank you @apollo13 |
Nomad's Task API provides every task managed by Nomad with a Unix Domain Socket (UDS) to access the local agent's HTTP API. Regardless of agent configuration the Task API does not require mTLS, but always requires authentication.
This would make it much easier when working with an mTLS enabled cluster 😇 and IIRC only requires a newer version of the Nomad API client.
https://developer.hashicorp.com/nomad/api-docs/task-api
hashicorp/nomad#16872
The text was updated successfully, but these errors were encountered: